Re^2: Application Error

Hi Marshall,

Thanks for your ideas.

I liked idea of naming your variables to render the comments useless very much. I don't know that I could always do it, because the names might become very long, but it's a good check to apply.

On the subroutines, I copied a bit of perl off the internet that I liked and it used the double underscore technique. I thought it was a good way of identfying subroutines very quickly and easily. Do you think it creates a problem?

Steve

Comment on Re^2: Application Error

Replies are listed 'Best First'.
Re^3: Application Error by Marshall (Canon) on Aug 14, 2009 at 18:26 UTC
Coming up with "good" variable names meaning: descriptive, understandable and "short" names is an art form. Practice matters. Your response reminded me of one the best ASM drivers I've ever read (from 30+ years ago). In those days limit was 5 letters, all CAPS for a var name. That was it! "ABCDE". I read this guy's code and I understood it. There were 2 comments in the ASM code: 1)"Suck it in" and 2) "blow it out". This guy was at a level that extremely few will ever achieve in terms of clarity, efficiency, brevity. I think we should ALL strive for descriptive names. I did some simple "translation" above. The underscore thing is a name space thing. I will defer to other Monks on the wisdom of that in OO modules. This is basically Perl OO thing that means that this is a private function that I my convention will not export and you should not call and thing with a name like that.	[reply]

Replies are listed 'Best First'.

Re^3: Application Error
by Marshall (Canon) on Aug 14, 2009 at 18:26 UTC

I think we should ALL strive for descriptive names. I did some simple "translation" above.

The underscore thing is a name space thing. I will defer to other Monks on the wisdom of that in OO modules. This is basically Perl OO thing that means that this is a private function that I my convention will not export and you should not call and thing with a name like that.

[reply]