| Re: IDL vs AWK input [message #33007 is a reply to message #32939] |
Thu, 21 November 2002 09:43  |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
I can relate to your frustration. I think this is an inevidable stage in
learning any programming language. Suggestions? Use another program if
you like it better; use none if you hate them all. Nobody can force you
to do what you don't want to do.
IDL's syntax *is* different. But there is also no other program that
envelopes as much within a single command. Don't believe me? Check out
WHERE and HISTOGRAM. Once you're over the steepest part of the learning
curve, you'll be cruising.
Cheers,
Pavel
Jason Quinn wrote:
>
> <IDL RANT ON>
> Wouldn't IDL be a trillion times better if it handled reading input in
> a style similar to awk, i.e. using $1, $2, etc., for reading in
> columns? IDL seems overdependant on format codes and the number of
> lines in a file. Also I'm sick of asking people how to do something
> simple with file input/output and instead of them telling me how to do
> it *in IDL* they direct me to some Joe Blow's webpage with a script
> that does it. I don't want some guy's script, I want to know how to do
> it in IDL. Am I a troll? No. I'm just fed-up with IDL's wacky syntax
> and half-baked feel and I needed to vent. IDL feels like a shaky house
> of cards. I know the way to do the things above, EOF, etc., but my
> point is that it's a poorly designed language. As a casual user, I
> basically need to relearn it every month or two because I've forgotten
> it in the meantime. The language is difficult to remember because it
> makes no sense.
> <IDL RANT OFF>
>
> Jason
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
