[jawsscripts] Re: quick constants protocol question
- From: Soronel Haetir <soronel.haetir@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Tue, 13 Jul 2010 04:44:16 -0800
All caps separated with underscore is inherited from C where that is a
fairly universal standard for most constant values. Not using the
underscore in that situation is somewhat odd (though of course there
are places you will see it).
So long as you are consistent you won't get a lot of complaints no
matter what you do.
On 7/12/10, Geoff Chapman <gch@xxxxxxxxxxxxxxxx> wrote:
> mighty longTime Scripters.
> In my brief forays into this crazy scripting world, for which I'm feeling
> less and less fitted as the days go on, but that's another story,
> I've found that sometimes, constants are written like this:
> c_myFavoriteFunkyThing
>
> presumably the C, up front, indicating the thing is a constant.
> Yet other times, I've seen this other horrible standard going on, where
> people will write the whole thing in upperCase, which to my mind is simply
> horrid! so far as firstPass comprehension Jaws speech output is concerned,
> like this:
>
> MYFAVORITEFUNKYTHING
>
>
> which I PERSONALLY abhor.
>
> TO ADD TO MY DISCUSSION,
> I've seen globals written sometimes with an underline separating the small g
> from the rest of the global definition, BUT other times, quite happily just
> small G for global, small letter denoting global type, i.e. s for string, i
> for integer etc, then a mixed case Delineated global name. like this:
>
> giTrunkAndTransfer
>
> which I like infinitely better!
>
> So, what I wanna know is, how horrifically renegade of me would it be, if I
> didn't want to follow either of these seemingly standard constant definition
> protocols, and do them more like global ones? such that we avoid Jaws having
> to waste precious time saying "underline,", but we still hear the c for
> constant, separately spoken before the mixed case Constant def? like this:
>
> cMyFavoriteFunkyThing
>
> how unacceptable would such an adoption be for me to make? and, why oh why,
> didn't everyone just adopt this one in the first place? since it's how
> globals seem to be quite happily defined? so there was already a good
> precedent there?
>
> I simply do dislike trying to work out what constants are, when they're all
> written in uppercase, and surely other speech users must've chafed under
> this restriction as well?
>
> thanks for any thoughts.
>
> oh, please do be gentle in your remonstrances if any are due me for these
> thoughts/desires eh.
>
>
> geoff c.
>
>
>
> __________�
>
> View the list's information and change your settings at
> http://www.freelists.org/list/jawsscripts
>
>
--
Soronel Haetir
soronel.haetir@xxxxxxxxx
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: