Front page | perl.bootstrap |
Postings from July 2000
Re: LALR
From:
Joshua N Pritikin
Date:
July 24, 2000 10:17
Subject:
Re: LALR
Message ID:
20000724131726.E3716@ghostwheel.wks.na.deuba.com
On Mon, Jul 24, 2000 at 01:00:28PM -0400, kstar@chapin.edu wrote:
> On Mon, Jul 24, 2000 at 12:43:09PM -0400, Joshua N Pritikin wrote:
> > On Mon, Jul 24, 2000 at 12:34:19PM -0400, jdporter@min.net wrote:
> > > That would tantamount to Perl (aka Larry, aka the Perl community) saying,
> > > "We were wrong, Java and Python were right." But we weren't wrong.
> >
> > Why can't perl ultimately support multiple syntax conventions? Why
> > can't the lexer/parser be pluggable?
>
> Why are you calling for a yacc interpreter? The lexer/parser _could_
> be pluggable, and this _might_ be a feature of the implementation, but why
> would you have this be a requirement of perl6 _per se_?
Some folks seem to prefer python syntax. I am simply repeating often
heard suggestions that perl be able to read a python-esque syntax.
Maybe this is a silly idea.
--
May the best description of competition prevail.
(via, but not speaking for Deutsche Bank)
-
RE: Threads, reentrancy, and suchlike things
by Moore, Paul
-
RE: Threads, reentrancy, and suchlike things (was: Re: Working Group Proposal)
by Moore, Paul
-
Re: Threads, reentrancy, and suchlike things (was: Re: Working Group Proposal)
by Benjamin Stuhl
-
Working Group Proposal
by Kurt D. Starsinic
-
RE: Threads, reentrancy, and suchlike things (was: Re: Working Group Proposal)
by Moore, Paul
-
Re: Threads, reentrancy, and suchlike things (was: Re: Working Gr oup Proposal)
by simon
-
Re: implementation strategy (was Re: Working Group Proposal)
by Benjamin Stuhl