[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [jelly@srk.fer.hr: Bug#57639: ucblogo: Bad short description?]



Michael Sobolev wrote:
> 
> On Fri, Feb 11, 2000 at 08:50:43AM -0500, Jeff Teunissen wrote:
> > Michael Sobolev wrote:
> > >
> > > On Fri, Feb 11, 2000 at 11:18:34PM +1100, Hamish Moffatt wrote:
> > > > > I believe this should be `a dialect of logo'...
> > > >
> > > > No, the man page says lisp too. There's no point in saying
> > > > "a dialog of logo" because that's obvious from the package name.
> > > Maybe the person who has written the man page was thinking about
> > > something else when he wrote it... :)
> >
> > LOGO _is_ a dialect of Lisp.
> Hmmm...  The last time I checked (6 years ago??) it was rather a
> procedural language, I may be wrong, though.

[from the comp.lang.logo FAQ]
1: What is Logo?

. . .

Logo is a dialect of LISP, notably one that a) eliminates much of the
need
for interminable nested parentheses and other notational nuisances found
in other LISPs, giving kids a simple notation consisting of prefix
function invocations and infix arithmetic, and b) adds to LISP a
graphical "turtle" and the accompanying finite differential geometry.

Why program in a dialect of LISP?

It's interactive and interpreted. Both interactive command lines and
user-written functions use a single notation that supplies immediate
results. There is no edit-compile-link-run cycle with its inherent delay
in providing results. Logo performs housekeeping operations such as
memory management transparently. The flip side for interpreters is that
they run slower than compiled native code, but Logo compiler systems have
begun to appear, and machines are always becoming faster.

. . .

-- 
| Jeff Teunissen -=- Pres., Dusk To Dawn Computing -- d2deek at pmail.net
| Disclaimer: I am my employer, so anything I say goes for me too.     :)
| dusknet.dhis.net is a black hole for email.    Use my Reply-To address.
| Specializing in Debian GNU/Linux         http://dusknet.dhis.net/~deek/


Reply to: