Re: Perl advocacy

[eejack]

One of the points I never see mentioned is being able to segment test and develop code.

For example you are building a simple system that takes user input from a form and puts it into a database.

With java - you need to build it, compile it, run it, and check the database.

With perl, you can code and test the routine that grabs the input. You can code and test the routine that builds the sql queries to put the data into the database. You can effectively code an entire system in parts, assemble and run.

I very often will work on one piece of a script at a time, and bash all the bits together when they all work. Can't do that with Java.

You certainly cannot build a one or two line piece of code to test regex's in Java.

Now in your situation, short - documented and runnable bits of code make training easier, and makes converting those *on the edge* easier.

Another neat touch would be make a java and perl version of the document, something that could put the document in a nice html format in their browser. Then show them the source code for each and (if possible) go through the steps to make a change or two. Edit-run vs edit-compile-run.

EEjack