Sebastian,
> I like hyphens. They're easier to type and help
> prevent_me_from_Doing_This and generating errors because
> of case sensitivity.
>
> On the other hand, consistency of appearance may be a
> problem for some people. I often associate code with the
> way it looks on screen, not necessarily with what it does
> or says. Looking for some_code_like_this() in a place
> that uses some-code-like-this() might be troublesome.
I think that is a valid concern, but I don't think it is
very troublesome. I don't think it takes long for your eyes
to adapt when switching between hyphens and underscores.
I would certainly agree, however, that mixing two styles in
a single file or, to a lesser extent, a single source tree,
would be troublesome. Not so much for the human readability,
but for the automatic searchability.
If you are standing on this piece of code
sub foo-bar ($a, $b) { say "whatever, I don't care" }
and perform a search for `foo-bar', you probably are not
going to expect this code a few hundred lines down:
foo_bar("this example doesn't have a theme")
This is a very valid concern, but the problem will not arise
unless people start mixing these two styles --- something
which is very obviously not a good idea.
Besides, another couple of hundred lines down, you might
(but you probably won't) find the following code:
eval ("foo", "bar").join("_")
In the end, this is a "suit yourself" kind of problem.
--
Daniel Brockman <[EMAIL PROTECTED]>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
