Using periods in sub and function names?

[TempodiBasic]

Hi
@TerryRitchie 
I have never used "." out of UDT, but this is  a my limit.

I'm glad to know and learn other ways to code and to create solution for specified problems!

@SMcNeill
this historical view of QB64 is interesting but also scaring in the thought that it is hard to have a complete clear view of QB64 code, a codemap that let correct or modify the code to get new or enpowered functions at sure shot!
Surely my hobbistic or inexpert point of view let you smile, but this is my reaction when I get those hiitorical informations about QB64.

[CharlieJV]

To me, periods are visual cues that I'm dealing with a variable that is of a compound type.

If I were working with a program with sub/function names that had periods in them, I would be immediately annoyed by the "semantic-meaning-overloading" of the period mark.

BTW:  If you like to use period marks in your identifier names, then you should use period marks in your identifier names.

As if I'm going to turn my nose up when presented with a gift of sample code ...

[madscijr]

Yes, they do resemble UDTs and that would get confusing to someone viewing the code. I'll stick with either camel case or underscores then.

I agree - let's not try to make things any more confusing!

[eoredson]

I often use periods in variables, such as:

  Color.Code = 14
  Color Color.Code, 0

without any difficulty except when in a udt:

  Type ColorCode
    Code As Integer
  End Type
  Dim ColorStruct As ColorCode
  ColorStruct.Code=14

Erik.