search

lf-lang / reactor-uc

A lightweight reactor runtime targeted at resource-constrained embedded systems
BSD 2-Clause "Simplified" License
2 stars 2 forks source link

Avoiding naming collisions #35

Open erlingrj opened 3 weeks ago

erlingrj commented 3 weeks ago

There is a problem that the name of types and structs defined in 'reactor-uc` might collide with user names. I think the only solution to this is to prepend something to our reactor-uc types and basically rename everything...

  1. lf_DelayedConnection
  2. lfDelayedConnection
  3. uc_DelayedConection
  4. ucDelayedConnection
  5. _DelayedConnection

What do you think?

edwardalee commented 3 weeks ago

I think we want to consistently use CamelCase or snake_case. snake_case is more common with C code.

erlingrj commented 3 weeks ago

Thanks for suggestion. I guess then either:

  1. LfDelayedConnection
  2. UcDelayedConnection

Would be right. The naming convention I went for was to Use CamelCase for structs/classes and snake_case for function names and variable names.

tanneberger commented 3 weeks ago

yes CamelCase for struct/classes

I prefer the 2.) UcDelayedConnection