From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4f316de357ae35e9
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-07-31 13:34:29 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!colt.net!kibo.news.demon.net!news.demon.co.uk!demon!pogner.demon.co.uk!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: FAQ and string functions
Date: 31 Jul 2002 21:16:47 +0100
Organization: Pushface
Sender: simon@smaug
Message-ID: <x7vfzxzsle8.fsf@pushface.org>
References: <20020730093206.A8550@videoproject.kiev.ua>
 <4519e058.0207300548.15eeb65c@posting.google.com>
 <20020731104643.C1083@videoproject.kiev.ua>
NNTP-Posting-Host: pogner.demon.co.uk
X-NNTP-Posting-Host: pogner.demon.co.uk:62.49.19.209
X-Trace: news.demon.co.uk 1028147567 nnrp-14:9371 NO-IDENT
 pogner.demon.co.uk:62.49.19.209
X-Complaints-To: abuse@demon.net
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Xref: archiver1.google.com comp.lang.ada:27533
Date: 2002-07-31T21:16:47+01:00
List-Id: <comp.lang.ada>

Oleg Goodyckov <og@videoproject.kiev.ua> writes:

> All of that I know. And all of that is very inconvinience to handle
> of strings. In Booch components set in demo files is present file
> bcwords.ada. Look at it. It contains full program for counting and
> printing of frequencies of words met in any given text file. But
> this file - bcwords.ada - begins from 15-line Perl's program, which
> does the same work. Look there, compare volumes of Perl's and Ada's
> programs, and think, why difference is so dramatically big in favor
> of Perl?

I didn't write Get_Next_Word (nor do I claim responsibility for the
problem that code has with improperly-terminated files :-)

I would be surprised if the part of the Perl code that *implements*
split was short.

When I *use* Get_Next_Word it only takes a line ...