comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Object Graphics Printing
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Object Graphics Printing [message #32705 is a reply to message #32664] Tue, 29 October 2002 07:32 Go to previous messageGo to previous message
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
On Mon, 28 Oct 2002 20:22:47 -0700, David Fanning wrote:

> Ben Tupper (btupper@bigelow.org) writes:
>
>> ;+
>> ; NAME:
>> ; FITASPECT
>
> And then,
>
>> FUNCTION Fit_Aspect, view, dest, $
>> margin = margin, Location = Location, $ Units = Units

> Apparently the distinction hinged on whether it is better to use capital
> letters in a natural and eye- pleasing way, or to sprinkle underscores
> all over God's creation. We'll let Ben have it both ways, since we don't
> want to confuse him. But what say the rest of you?

Interestingly, almost all contemporary coding style suggestions for
modern languages I could find specify visually segregating function
calls from variables by using MixedCasePascalStyle for one and
lower_case_underscore for the other. I've rarely seen an advocate of
both styles throughout. That said, I think the overuse of
capitalization is a grievance not to be taken lightly, one which most
net users have learned, often by harsh rebuke, is TANTAMOUNT TO
SHOUTING. Purveyors of this false truth can usually be excused as
having been damaged early on by over-exposure to FORTRAN (ditto for
GOTO). None of the coding style guidelines I've found recommend
significant use of ALL-CAPS.

I weigh in on the side of the quieter, less visually obstreperous use
of lower case variables and identifiers, saving upper case for spare
and special purposes like certain comparisons (AND, OR, EQ, NOT) and
keywords (device,/COLOR), which might otherwise get lost in the line
noise. I like MixedCase (but not uppercase) Methods, and lower-case
for most functions (except those associated with methods, or OO-like
bundles of code). And I use syntax coloring, which both IDLDE and
IDLWAVE do with aplomb, to provide additional visual differentiation.

Just the opinion of one,

JD

P.S. A comparison of the styles remains at:
http://turtle.as.arizona.edu/idlstyle.html
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: LJPEG decopression
Next Topic: Re: LJPEG decopression

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Dec 03 20:07:29 PST 2025

Total time taken to generate the page: 0.22372 seconds