Re: Now, to try again... by Dan Sugalski- December 18, 2000 At 12:29 PM 121800 +0000, David Grove wrote:>Sam Tregar <samtregar.com> wrote:>> > On Mon, 18 Dec 2000, David Grove wrote:> >>>snip>> > > _Perl_ _within_ _a_ _Perl_ _context_ _and_ _for_ _Perl_ _purposes_,> >> > Feeling a little hostile to the rest of the programming world You&39;re> > sounding almost nationalistic! We&39;re not at war.>>No no. I just think we&39;ve redefined the "little languages" as...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg199.html Re: Now, to try again... by David Grove- December 18, 2000 Sam Tregar <samtregar.com> wrote: > On Mon, 18 Dec 2000, David Grove wrote: >snip > > _Perl_ _within_ _a_ _Perl_ _context_ _and_ _for_ _Perl_ _purposes_, > > Feeling a little hostile to the rest of the programming world You&39;re > sounding almost nationalistic! We&39;re not at war.No no. I just think we&39;ve redefined the "little languages" as everestsrather than molehills. That scares me.I also admit that I would, on a purely personal-bias level, prefer.http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg198.html Re: Now, to try again... by David Grove- December 18, 2000 Nicholas Clark <nickccl4.org> wrote: > On Mon, Dec 18, 2000 at 11:30:09AM +0000, David Grove wrote: > > > > Bart Lateur <bart.lateurskynet.be> wrote: > > > > But, the gist of this post is: we don&39;t want to loose theusefulness > of > > > the syntax highlighter, as soon as there is one syntax error inthe > > > script, because this will be the normal situation while editing > source. > > > Parsers are generally very bad.http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg197.html Re: Now, to try again... by Nicholas Clark- December 18, 2000 On Mon, Dec 18, 2000 at 11:30:09AM +0000, David Grove wrote:> > Bart Lateur <bart.lateurskynet.be> wrote:> > But, the gist of this post is: we don&39;t want to loose the usefulness of> > the syntax highlighter, as soon as there is one syntax error in the> > script, because this will be the normal situation while editing source.> > Parsers are generally very bad at parsing erroneous code.> > You&39;re forgetting something. Any such editor would have..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg196.html Re: Now, to try again... by Sam Tregar- December 18, 2000 On Mon, 18 Dec 2000, David Grove wrote:> For the full language spec, I don&39;t think it&39;s attainable, and honestly> don&39;t see the reason for it within the context of Perl.I&39;ve got a simple reason for it - I think it&39;s going to be part of thePerl6 spec. Do I have any proof Nope. We&39;ll know when Larry&39;s finishedwith the Perl6 spec.What about this work do you see an unatainable We&39;re really just talkingabout defining an API for people to hook into the Perl 6 parser..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg195.html Re: Now, to try again... by David Grove- December 18, 2000 Bart Lateur <bart.lateurskynet.be> wrote: > On Sun, 17 Dec 2000 14:11:50 -0700 (MST), Nathan Torkington wrote: > > >I think the problems with this that were raised in the past are: > > parsing partial source > > does this mean that the parser has to reparse the whole sourcefile > > every time you type a character > > Hold it. I don&39;t think that is very practical, and for more than one > reason.snip > But, the gist of this post is: we...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg194.html Re: Now, to try again... by David Grove- December 18, 2000 Andy Dougherty <dougheralafayette.edu> wrote: > The issues of &39;use Python&39; or &39;use Pythonish&39; are a quite differentissue. > I don&39;t think anyone believes it ought to be easy to write thePythonish > module.I do.That&39;s the problem. This is a nearly ubiquitously desired objective(writing the modules or whatever they are), but I have the fear thatactually writing one will be so undaunting that it will be a seldom-usedfeature, or one that will be as often avoided as..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg193.html Re: Now, to try again... by David Grove- December 18, 2000 Andy Dougherty <dougheralafayette.edu> wrote: > > That sounds too complex for what seems like a more simple solution.When > > you say "turn simple &39;languages&39; into perl", that&39;s what Dan&39;s toldme is > > my source filter. > > Correct. perl-byacc is a source filter. It takes in yacc source and > outputs perl code. It just may not be what folks first think of as a > "source filter" in the sense of using the Filter:: modules. ...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg192.html Re: Now, to try again... by Nathan Torkington- December 18, 2000 Another point re: the parsing process. I think it should be possiblefor any of the steps or extensions to be defined as C code or as Perlcode. We&39;re already shooting to have C subs isomorphic with Perl subsso this shouldn&39;t be a problem, just something to keep in mind.Nathttp://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg191.html Re: Now, to try again... by Chaim Frenkel- December 18, 2000 >>>>> "NC" == Nicholas Clark <nickccl4.org> writes:NC> I&39;m assuming that for performance reasons a parser-beast written in C wouldNC> have code to do this conditionally compiled (like the -DDEBUGGING stuff)NC> so that serious production perl wouldn&39;t have the slowdown, but the perlNC> you embed in your favourite editor would. It could even tell you the NC> precise character (rather than line number) that it barfed on. It couldNC> run perl...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg190.html |