Re: Now, to try again... by David Grove- December 18, 2000 Sam Tregar <samtregar.com> wrote: > On Sun, 17 Dec 2000, David Grove wrote: > > > Ok, my C&39;s rather rusty, but are we interested in parsing that > > Yes. I&39;ve heard people talk about a C frontend. Will it ever see the > light I don&39;t know. Does it matter I don&39;t think so.Sorry, Sam, my strong cynicism (realism ) is not directed at anyonespecifically. The term "little language" has been redefined, and, takingall other posts and goals into...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg189.html Re: Now, to try again... by Andy Dougherty- December 18, 2000 On Sun, 17 Dec 2000, Dan Sugalski wrote:> At 02:24 PM 121700 -0500, Sam Tregar wrote:> >It comes down to what is meant by "little language". When I hear that> >term I immediately think Scheme and TCL. > For my part, at least, I&39;ve been thinking of something either LISP-ish or > very simple parameter settingchecking (like stuff in, say, your average > .rc file with a little control flow thrown in) when it&39;s brought up. That&39;s typically what I think...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg188.html Re: Now, to try again... by Bart Lateur- December 18, 2000 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 characterHold it. I don&39;t think that is very practical, and for more than onereason.For the editor I&39;m currently using, the Perl syntax coloring is a bitsimple minded, in that it does its syntax highlighting on a line by...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg187.html Re: Now, to try again... by Andy Dougherty- December 18, 2000 On Sun, 17 Dec 2000, David Grove wrote:> > "Little languages", on the other hand, are a somewhat different matter.> > They will presumably be not-so-complex and hence won&39;t require such> deep> > hooks, and some redundancy there won&39;t be such a big problem.> > I&39;m not sure how this is incongruent with your first paragraph. Could you> elaborate a bitYou had expressed concern about redundancy if each parser had tore-implement a whole slew of...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg186.html Re: Now, to try again... by David Grove- December 18, 2000 Sam Tregar <samtregar.com> wrote: > possible, right Are you saying you don&39;t think we should make it > possible for someone to write a C parser for PerlFor the full language spec, I don&39;t think it&39;s attainable, and honestlydon&39;t see the reason for it within the context of Perl. It doesn&39;t makesense to me that we would want Perl6 to have the ability (though notnecessarily do it, just the ability to do it if someone has the notion) to_replace_ python, gnu c, java sdk,..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg185.html Re: Now, to try again... by Nicholas Clark- December 18, 2000 On Sun, Dec 17, 2000 at 02:11:50PM -0700, Nathan Torkington wrote:> Nicholas Clark writes:> > Would it be sane to get the parser to return suitable information on the> > source to let a syntax analyser (such as a highlighting editor) know that> > character positions 5123 to 5146 are a qq() string (So it can change the> > font or the colour or whatever)> > I think the problems with this that were raised in the past are:> parsing partial sourceIf I understood.http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg184.html Mail problems simoncozens.net: Re: Now, to try again... by Simon Cozens- December 18, 2000 This is the fourth time I&39;ve sent this mail to perl6-internals-api-parser,but it doesn&39;t seem to be arriving. None of my other mail is affected, andperl5-porters is, for once, behaving itself; why this list in particular ----- Forwarded message from Simon Cozens <simoncozens.net> -----Damn this is annoying. Is it perl.org that&39;s dropping mail or me----- Forwarded message from Simon Cozens <simoncozens.net> -----On Sat, Dec 16, 2000 at 08:09:23PM +0000, David Grove...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg183.html Re: Now, to try again... by Simon Cozens- December 18, 2000 Damn this is annoying. Is it perl.org that&39;s dropping mail or me----- Forwarded message from Simon Cozens <simoncozens.net> -----On Sat, Dec 16, 2000 at 08:09:23PM +0000, David Grove wrote:> Thinking of just the parser as a single entity seems to me to be headed into> trouble unless we can define in advance what type of role these dialects> will play in the language, and at what point they merge into a single entity> and how.I can understand each word in this sentence, but..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg182.html Re: Now, to try again... by Sam Tregar- December 17, 2000 On Sun, 17 Dec 2000, David Grove wrote:> Ok, my C&39;s rather rusty, but are we interested in parsing thatYes. I&39;ve heard people talk about a C frontend. Will it ever see thelight I don&39;t know. Does it matter I don&39;t think so.> Is Perl going to provide API to access pointers through source> codePerl 6 wouldn&39;t be the first to do so for Perl if it did. Check out SWIG.I&39;m guessing that&39;s not the route that a C frontend for Perl would takebut who knows!> The...http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg181.html Re: Now, to try again... by David Grove- December 17, 2000 Sam Tregar <samtregar.com> wrote: > On Sun, 17 Dec 2000, Dan Sugalski wrote: > > > For my part, at least, I&39;ve been thinking of something eitherLISP-ish > > or very simple parameter settingchecking (like stuff in, say, your > > average .rc file with a little control flow thrown in) when it&39;s > > brought up. Occasionally things FORTHish, but only when I really > > desperately need sleep. :) > > Sounds like Scheme and TCL to me. Ok, it&39;s..http://www.nntp.perl.org/group/perl.perl6.internals.api.parser/2000/12/msg180.html |