How about giving us the new keywords and a little about what they
control and we could probably come to a consensus?  Either that, or just
think to yourself, if I was just using the program and not writing it,
what would make sense to me.

I think some good examples are the keywords for radiosity.  Like
grey_threshold could just be grey.  100% grey is no color.  Simpler but
makes sense.  I think minimum_reuse could just be reuse.

I agree with Ron that it's customary for reserved keywords to use all
lowercase and user defined terms should start with a Cap.  So be
specific.  People can change variable names that conflict with them;
that's what the message window is for. ;)

-Mike

> Anyone else out there have any opinions on this... right now I have a lot of
> keywords WITH underscores... my reason for this is that the more specific
> I make the keyword, the less likely it will be that it conflicts with
> somebody's variable name.  You know... now that I think about it, maybe I
> should ditch some of those extra-long keywords.  (One of the reasons I
> dislike COBOL is the long keywords.)  If somebody wants to use one of my
> reserved words for a variable name, too bad.  ;-)
> 
> -Nathan

Post a reply to this message