Stories
Slash Boxes
Comments

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

use Perl

All the Perl that's Practical to Extract and Report

natural language processing More | Login | Reply

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

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Obvious ? (Score:2)

by rafael (2125)

I'm afraid I don't see why perl would be an obvious choice -- this application uses probably some high level algorithms for which the language features are mostly irrelevant. (Although perl would be certainly a very good choice.)
- Re:Obvious ? (Score:2)
  
  by TeeJay (2309) on 2003.10.24 11:22 (#25155) Homepage Journal
  
  Perl is better at adhoc objects and data structures, it also makes the low level elements that make up the high level algorithms (tokenizing, etc) fairly trivial.
  To me perl would be very well suited, unfortunately many people just use java because they don't know that a better suited tool is available (although often it would be quicker for them to write a huge application in java than to learn enough perl to write a simpler faster version in perl)
  
  --
  
  @JAPH = qw(Hacker Perl Another Just);
  print reverse @JAPH;
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.