On Oct-07, Dan Sugalski wrote:
> At 9:55 PM +0200 10/7/04, Leopold Toetsch wrote:
> >Steve Fink <[EMAIL PROTECTED]> wrote:
> >
> > > Clearly, I'm not very experienced with dealing with these things across
> >> platforms, so I was hoping somebody (Andy?) might have a better sense
> >> for what these
Hey all,
Here's a simple hand coded example that
(correctly, AFAIK) prints "ab" in vanilla
parrot, but goes off in an infinite
loop with the --python flag.
Why does --python mode modify the
behaviour of coroutines?
I thought perhaps they were used for
generators or "for...in" iteration, but
th
gensym, hehe. History repeats ;-)
- Michael
On Thu, 07 Oct 2004 21:49:22 -0400, William Coleda <[EMAIL PROTECTED]> wrote:
> A macro example in the docs shows:
>
> .macro swap (A,B,TEMP) # . marks the directive
> set .TEMP,.A # . marks the special variable.
> set .A,.B
> se
btw, thanks to whoever fixed macros so that they could be defined outside of .sub's.
Very handy.
A macro example in the docs shows:
.macro swap (A,B,TEMP) # . marks the directive
set .TEMP,.A # . marks the special variable.
set .A,.B
set .B,.TEMP
.endm # And . marks the end of the macro.
Is there a way to write this macro without specifying the TEMP paramete
On Sun, 3 Oct 2004, Jeff Clites wrote:
> I think that no matter what the approach, there's an unavoidable
> mismatch between Perl and Python when it comes to variable naming, it's
> going to be a bit awkward to access Perl variables from within Python.
...
> 1) Treat Perl variables as having the s
On Thu, 07 Oct 2004 09:45:19 -0700, Steve Fink wrote:
> I've been struggling with getting Darwin to build the dynclasses/ stuff,
> and I seem to have it working now. (Oh, and it fixes the Linux build
> too.) It's a fairly large change, and I would like to use standard
> naming conventions througho
So... how does one use AST?
There's a list of functions in `perldoc ast/node.c`, but that seems to be it. (nothing
in docs or t). I don't see that it's used anywhere outside of ast/* ...
Is this a C-only interface? If so, any plans to make PMC or opcode wrappers?
"Ron Blaschke (via RT)" <[EMAIL PROTECTED]> wrote:
> Does anybody know about (or is working on) this?
>
> Compiling with:
> xx.c
>
cl -nologo -GF -W3 -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -DNO_HASH
_SEED -Zi -I./include -IC:\usr\loc
> al\icu\include -DHAS_JIT -DI386 -I. -Fo xx.obj -c xx.c
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #31884]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31884 >
Does anybody know about (or is working on) this?
Compiling with:
xx.c
cl -nologo -GF
At 9:55 PM +0200 10/7/04, Leopold Toetsch wrote:
Steve Fink <[EMAIL PROTECTED]> wrote:
[ snip explanation ]
So what I need is names for these. At the moment, I'm mostly using $(SO)
for shared lib extensions, $(DYNMOD) for d-l-modules. The buildflags I
gneerally call $(LD_SHARED) or something wit
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #31883]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31883 >
Replaced
%.pbc:%.imc
with
.pbc.imc:
as former is not supported by nmake.
config/gen/
Steve Fink <[EMAIL PROTECTED]> wrote:
[ snip explanation ]
> So what I need is names for these. At the moment, I'm mostly using $(SO)
> for shared lib extensions, $(DYNMOD) for d-l-modules. The buildflags I
> gneerally call $(LD_SHARED) or something with shared for shared libs,
> and something li
I've been struggling with getting Darwin to build the dynclasses/ stuff,
and I seem to have it working now. (Oh, and it fixes the Linux build
too.) It's a fairly large change, and I would like to use standard
naming conventions throughout, but I haven't really found any
convincing, definitive sourc
Short version: an installed Parrot is now able to locate its ICU data.
The longer story: During "make" a new file src/parrot_config.c is
created holding currently just one entry: the install --prefix directory.
During string_init that directory is stat()ed and when the *directory*
exists, ICU dat
On Oct 6, 2004, at 11:49 PM, Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
3) I won't mention the problem of languages which allow an object to
have instance variables and instance methods of the same name (so that
in Python, "a.b" would be ambiguous if "a" is an object from such a
Jeff Clites <[EMAIL PROTECTED]> wrote:
> 2) I'd expect the method cache to be per-class, but Python can change
> an attribute slot on a per-instance basis (as well as a per-class
> basis), so we can't really use a per-class method cache (or, we need a
> flag on particular instances which tell us n
17 matches
Mail list logo
