Re: Re: Is there ever a time Perl is the wrong choice?

There are great modules for these things. The stuff that needs to be fast is written in C while a Perl framework holds it together.

Perl isn't great at numerical analysis. For example, if you have a 1024x1024 matrix (possibly for a fourier analysis) it will eat up far more memory in perl than it will in C/C++

PDL is great for 1024x1024 matrices.

Low level image processing in perl isn't that great either. There are a lot of modules in CPAN that interface to external utilities (like Image::Magick).

Imager is not an interface for external stuff.

I can't really imagine anyone wanting to write a device driver in perl :)

I'd like to be able to. Lots of devices don't need speedy drivers, and it'd be a great way to prototype!

There might be really good ways to do all of these things with modules.

There are indeed!

Juerd
- http://juerd.nl/
- spamcollector_perlmonks@juerd.nl (do not use).

Comment on Re: Re: Is there ever a time Perl is the wrong choice?

Replies are listed 'Best First'.
Re: Re: Re: Is there ever a time Perl is the wrong choice? by PrakashK (Pilgrim) on Feb 06, 2003 at 20:02 UTC
Imager is not an interface for external stuff. A large part of Imager appears to have been implemented in C. /prakash	[reply]
Re: Re: Re: Re: Is there ever a time Perl is the wrong choice? by Juerd (Abbot) on Feb 06, 2003 at 23:02 UTC
A large part of Imager appears to have been implemented in C. The larger part of Imager is indeed implemented in C. So is most of PDL. Have you read the first paragraph in my post? Yes, much is coded in C, but they're still Perl modules. Data::Dumper is coded partly in C - does that bother you at all? Juerd - http://juerd.nl/ - spamcollector_perlmonks@juerd.nl (do not use).	[reply]