On Wed, Nov 23, 2005 at 09:09:00AM -0500, Will Coleda wrote:
> >Why bother with an artifical subclass?
>
> Mainly to avoid having the C code in my .pmc
I'm very much in favor of adding explicit metadata, which is
parseable, rather than just limiting ourselves to writing the
executable consequence
Roger Browne wrote:
A bigger problem will occur for any HLL that has no PMCs of its own, yet
wishes to use DynLexPad. How to specify that?
As coke writes this is in the intial posting of this thread, but he has
cited only half ot the show. Here is all again:
SYNOPSIS
.sub _load :immediat
I thought that was one of the issues leo was addressing with
the .HLL_map directive... From leo's initial email:
.HLL "foo", "" # or "foo_group" - load dynamic PMCs too
.HLL_map .LexPad -> .DynLexPad # (2)
Regards.
On Nov 23, 2005, at 9:28 AM, Roger Browne wrote:
On Wed,
On Wed, 2005-11-23 at 09:09 -0500, Will Coleda wrote:
> I can, of course, add the C now, and have it be functional. I was
> just pondering what might be a simpler way for future PMC authors.
A bigger problem will occur for any HLL that has no PMCs of its own, yet
wishes to use DynLexPad. How to
On Nov 23, 2005, at 4:39 AM, Roger Browne wrote:
On Tue, 2005-11-22 at 22:42 -0500, Will Coleda wrote:
.HLL "foo", "" # or "foo_group" - load dynamic PMCs too
.HLL_map .LexPad -> .DynLexPad # (2)
I'd like to provide an easy way to provide this mapping for language
develop
On Tue, 2005-11-22 at 22:42 -0500, Will Coleda wrote:
> > .HLL "foo", "" # or "foo_group" - load dynamic PMCs too
> > .HLL_map .LexPad -> .DynLexPad # (2)
> >
>
> I'd like to provide an easy way to provide this mapping for language
> developers so the users of the language don
On Nov 23, 2005, at 4:42, Will Coleda wrote:
I'd like to provide an easy way to provide this mapping for language
developers so the users of the language don't have to remember to add
the second line whenever they use, e.g. Tcl.
Whenever some code is using e.g. Tcl, a library is loaded that
On Nov 22, 2005, at 11:06 AM, Leopold Toetsch wrote:
dynclasses/dynlexpad.pmc provides (or should eventually provide) a
more dynamic lexpad (similar to the deprecated scratchpad.pmc).
It's not finished yet, it doesn't consult LexInfo for static
lexicals yet.
Before working more on it, I'
On Nov 22, 2005, at 19:52, Chip Salzenberg wrote:
On Tue, Nov 22, 2005 at 05:50:39PM +, Roger Browne wrote:
Why not use "," instead of "->"?
Indeed. We shouldn't introduce "->" at this point, when we already
use the perfectly serviceable comma for analogous cases.
Done, r10140.
leo
I wrote:
> > I'd prefer to ask for mappings explicitly, e.g. something like this:
> >
> >.HLL "Tcl", "tcl_group"
> >...
> >$P0 = new Integer # really Integer
> >$P1 = new_mapped Integer # really TclInteger
Chip wrote:
> Hm. Why?
Because you don't always want a mapped ty
On Tue, Nov 22, 2005 at 05:50:39PM +, Roger Browne wrote:
> Leopold Toetsch wrote:
> > .HLL_map .LexPad -> .DynLexPad # (2)
>
> Why not use "," instead of "->"?
Indeed. We shouldn't introduce "->" at this point, when we already
use the perfectly serviceable comma for analogous ca
Leopold Toetsch wrote:
> Before working more on it, I'd like to know from HLL authors, what they
> need.
I don't think I need anything more than :outer and .lex for the Amber
compiler. I certainly don't need to specify or manipulate pad_depth.
> .HLL_map .LexPad -> .DynLexPad # (2)
12 matches
Mail list logo
