Derek Lamb <[email protected]> wrote: > 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.
Yes absolutely. If you look at my other email in this thread you'll see that I feel similar. Specifically, I think that: #!/usr/bin/perldl ... Should be exactly equivalent to: #!/usr/bin/perl use PDL; use PDL::Autoload; use PDL::NiceSlice; ... So it basically becomes a short-cut, but it otherwise 100% Perl. It keeps Perl Perl. After all, Perl is what makes PDL interesting compared to all the other alternatives. The idea here is that this change would make PDL more natural for a new user coming from Matlab or IDL, without losing any of the Perliness that makes PDL interesting int the first place. > 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. Well, I think this would miss the point. If I know enough about Perl and PDL to hack its environment, I probably don't need the hack in the first place. Instead, pretend you are talking to a Matlab geek who doesn't know anything about Perl except that it looks like line noise. Daniel. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
