NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

## All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Full
Abbreviated
Hidden
• #### Tools that work(Score:1)

Actually, this sounds like a success to me! A high-level tool that is so successful that you don't need to read the specs for the low-level tool? That's a successful abstraction.

• #### Re:(Score:1)

You have a different definition of "success" that I do.

• #### Re:Tools that work(Score:1)

by ChrisDolan (2855) on 2008.09.06 21:02 (#64799) Homepage Journal

By success, in this case I meant that someone did not need to learn something that was not relevant to getting his/her work done. Of what benefit is knowing the classpath syntax for command-line Java? Analogy: using Perl makes knowing the order of arguments of the malloc function useless. Automatic memory management is a success for Perl, like automatic project management is a success for Eclipse.

For reference, that classpath syntax is actually simple, but platform-specific (colon or semi-colon as path separators!). On Windows: java -cp path\to\file.jar;another.jar ..., on pretty much all other platforms: java -cp path/to/file.jar:another.jar. In Ant, it's actually MUCH more complicated, involving path tags with nested pathelement tags, but it is platform-independent, happily.

• #### Re:(Score:1)

Ah...at that level sure. But you are taking it to the tool level which is where your Perl analogy falls apart. eclipse is not Java and "I" would think a Java programmer would know the classpath syntax.

• #### Re:(Score:1)

You only see the difference because the Perl project-management tools aren't good enough yet.

We'll be fixing that.