OpenEuphoria

Re: party cancelled

• Posted by Robert B Pilkington <bpilkington at JUNO.COM> Sep 11, 1998
• 540 views

[CasE SensiTiviTy]
>I think that case sensitivity is a good thing. What I find is that I
>try to make my code self documenting by choosing nouns for variable
>names and verbs for procedure and function names, and that I often
>run out of synonyms for closely related items. Often enough too,
>the appropriate word is already in use as a reserved keyword. The
>ability to distinguish words by case give a much larger number of
>useable names that are suggestive of the action they are associated
>with.
>
>The only argument I can see against case sensitivity is just that
>people have trouble typing capitals - you know - hitting two keys at
>once requires advanced digital coordination.

Fact: Programming uses lots of shift characters. That's why we make the
big bucks.  (Well, sorta... just take out the 'big', and maybe the
'bucks'...)

I think case sensitivity is good, if keeps you from writing "ThIs" in
some places, and "This" in others, and "this" in still other places, all
meaning the samething. Instead, you can use all those as different
variable names! 

Also, if you don't want to make your variable/constants/subroutines use
uppercase letters, don't. It's as simple as that.

Okay, so I don't see this coming to an end, there's no good argument on
either side. Let's just keep it as is so it gets compiled faster. (There,
we win! 

[constant CONSTANT]
>Why would anybody mind constants? If you use them they're handy, if
>you don't they are not. Why deny them to those who like them?

Constants are good. Code that uses constants like PI will run just as
fast as programs that replaces the constant with the number, 3.14(more
numbers), and be more readable. Plus, if for some reason PI should happen
to change, you only have to change one number in the code . . .

[SHIFT+characters]
>Is there a proposal for a substitute for curly brackets? There aren't
>all that many non-alphanumeric keys on my keyboard that don't need a
>shift.

This is also why the suggested {30 (50+40) (40-3) -5} will fail. It
requires more shift9 and shift0's than the old style commas. 

The reason the curly braces are used, is because that's what's used in C
for similar stuff:

// C code!
// Don't remember if this only works for constants or not, but I have
// done this with either variables or constants.
int sequence[5] = {0, 1, 2, 3, 4};
// Ah, safe

(Now somebody is going to bring up variable initializations in the
declaration, ie integer x=0, which I can agree with.)


_____________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]