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.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Friday October 24, 2003
04:37 AM

natural language processing

[ #15368 ]
LingPipe looks quite cool.

Shame its java, but they have plenty of info and white papers on the site

Its puzzling that things like Lucene and this are appearing in Java when perl would seem the obvious choice for language processing.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.)
    • 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;