On 05/04/2010 05:00 PM, Daniel Carrera wrote: > But then you'd have to include that in every file, right? > > Here is another idea: Make the "perldl" program able to receive a PDL > script as input and execute it. > > ~ $ perldl myprogram.pdl > > > This could be rather cool. The perldl binary could auto-include basic > modules like PDL, PDL::AutoLoader and PDL::NiceSlice. Make ".pdl" the > "standard" extension to distinguish it fro regular Perl scripts. > > Now you have something that really feels like a stand-alone numerical > analysis language, in the style of MATLAB and IDL. > > What do you think? > Remember that while PDL is an extension to Perl, it's not necessarily the end of the road. For example, you could write a script that would query a database, feed the result into piddles, perform some computation, create an image or plot, and then write out a webpage. So just because you're using PDL doesn't necessarily mean it's distinct from Perl. Nevertheless, many people use .pdl as their extension on files that mostly use PDL.
Check out 'the pdl environment' on the wiki. This will show you how to set up commands to run every time you launch perldl (including loading modules), how to tell AutoLoader where to search for scripts, how to get syntax highlighting of .pdl files in Emacs. I think this will help you get the "feel" you are looking for. best, Derek _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
