|
|
Posted by Shelly on 07/30/06 21:04
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:RridnQZk68UkUFHZnZ2dnUVZ_vSdnZ2d@comcast.com...
> Shelly wrote:
>> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
>> news:-o2dnUSBY-LaCFbZnZ2dnUVZ_sudnZ2d@comcast.com...
>>
>>>But if you're never worked on a multi-programmer project in a case
>>>sensitive language you may not understand the benefits.
>>
>>
>> Jerry, I think you caught the real reason here. I'm disappointed at
>> myself that I didn't think of it. It is the MULTI-programmer aspect that
>> brings in the real need for enforcing conventions.
>>
>> Shelly
>
> Shelly,
>
> Yes, it is much more important in multi-programmer projects.
>
> For instance, when looking at someone else's code, I can tell that
> 'Employee' is a class object, while 'anEmployee' is an object of the
> Employee class, and employee[] is an array of Employee objects. And when
> everyone uses the same conventions, you have less chance of conflicts
> between different programmers.
>
> And sure, I know you can add comments to explain the code. And I'm not at
> all against comments - I encourage their use. But at the same time I'm a
> big promoter of having the code document itself as much as possible, and
> conventions like these help.
>
> Case sensitivity can really help with code clarity, if it's used properly
> and conventions are followed.
Did you write all this or did I? It could have been from either of us.
Shelly
Navigation:
[Reply to this message]
|