Piers Cawley <[EMAIL PROTECTED]> wrote:
> Don't trace system areas in sweep ops
> through holes in the C stack (hmm... if anyone has a good drawing of
> this?)).
I don't know if its a good one, but my original posting about that
problem had some ASCII graphics (in this thread):
Subj
On 2003-08-05 at 16:10:46, Dan Sugalski wrote:
> At 1:02 PM -0700 8/5/03, Dave Whipp wrote:
> >Can I discriminate on parameter names using multi subs?
>
> Nope. Named parameters don't participate in MMD.
1. I'm thinking MMD should be called something else when being applied
to multisubs rather
- Original Message -
From: "Michal Wallace" <[EMAIL PROTECTED]>
To: "Leopold Toetsch" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, August 12, 2003 5:46 AM
Subject: Re: pirate status / need help with instances
> On Tue, 12 Aug 2003, Michal Wallace wrote:
>
> > I wound up g
On Tue, 5 Aug 2003 12:48, Michal Wallace wrote:
> It does seem like there are some snags getting
> languages to talk to each other, even with the
> calling conventions, but even so, I'm even more
> convinced now that a generic, overridable
> code-generator is the way to go.
>
> It seems to me that
- Original Message -
From: "Joseph Ryan" <[EMAIL PROTECTED]>
To: "Michal Wallace" <[EMAIL PROTECTED]>
Cc: "K Stol" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, August 05, 2003 12:24 AM
Subject: Re: generic code generator? [was: subroutines and python status]
> Michal Wallace w
Michal Wallace wrote:
On Sun, 3 Aug 2003, K Stol wrote:
What do you think? Want to try squishing pirate/python
and pirate/lua together? :)
Yeah, I like the idea. Let's try this out.
Well, I finished reading your report[1] and
posted some of my (rather unorganized) thoughts
up at
Kenneth Graves <[EMAIL PROTECTED]> wrote:
> (I'd like to have
> $P0 = new $S0
> do what I want. Failing that, I'd at least like the find_type workaround.)
That should be done here:
| target '=' NEW classname COMMA var { $$ = iNEW(interp, ...
| target '=' NEW classname{ $$ = iNEW(
david nicol wrote:
> [EMAIL PROTECTED] perl -le '$_{a}=27; package notmain; print $_{a}'
> 27
>
> Gosh!
>
> Let's document it! Would it go in perlvar or perlsyn?
It's already documented, in perlvar/"Technical Note on the Syntax of Variable Names"
(at the end)
Simon Glover wrote:
Why not just use a macro?
# .macro fortytwo (A)
#set .A, 42
# .endm
#
# .fortytwo(I0)
# print I0
# print "\n"
# end
Simon
Shouldn't be The Answer a builtin?
Kay
This is really a language feature; you should add it to the hq9+
implementation.
--
Gordon Henriksen
IT Manager
ICLUBcentral Inc.
[EMAIL PROTECTED]
> -Original Message-
> From: Jos Visser [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 07, 2003 11:21 AM
> To: Perl6 Internals (parro
> Out of curiosity, how does the word
> "assign" imply that it morphs an
> existing value, and how does the word
> "set" imply that it copies a pointer?
Well, I suppose "set" was chosen just because
that seems to be the standard name for an
operation that copies a pointer. Then "assign"
was chosen
At 11:48 PM +0200 8/5/03, Leopold Toetsch wrote:
Simon Glover wrote:
At 12:18 PM +0200 8/5/03, Leopold Toetsch wrote:
First: any changes here imply, that assemble.pl/disassemble.pl will
seeze to work.
Well, there's disassemble.c, which pdb uses; does that do everything
that you want?
All pack
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23252]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23252 >
Some refactoring in the seek/tell system.
Seek and tell now use both PIOFF_T for the
Having read this thread, I think that the real problem is not just that
there are multiple assignment semantics -- it's that the names "set" and
"assign" are not really meaningful -- that is, they *look* to english
speakers as if they are synonyms... their names alone aren't enough info
to know wh
John Siracusa <[EMAIL PROTECTED]> writes:
> Did this ever get resolved to anyone's satisfaction? While reading
> EX6, I found myself wonder exactly what for() would look like in
> Perl 6 code...
A for loop[1] is basically syntax sugar for a while loop. In general,
where foo, bar, baz, and quux
At 10:01 PM +0300 8/8/03, Vladimir Lipskiy wrote:
> At 9:21 PM +0300 8/8/03, Vladimir Lipskiy wrote:
> > So, the project. Someone needs to go through the configure procedure
>> and the headers and throw a PARROT_ prefix in front of all the HAS_
>> defines we define, so we can avoid this prob
On Aug-07, Simon Glover wrote:
> In other words, if we're referencing an element outside the current
> array bounds, then we call undef(), which creates a new PerlUndef PMC,
> and we then use this _solely_ to call get_integer on, despite the fact
> that we _know_ that the result is going to be
On Thu, Aug 07, 2003 at 05:21:11PM +0200, Jos Visser wrote:
> Accompanying patch adds the "fortytwo" op to Parrot, so the following
> PASM becomes legal:
>
> fortytwo I0
> print I0
> print "\n"
> end
>
> Example:
>
> $ ../parrot test42.pasm
> 42
>
> Sorry, could not res
Togos <[EMAIL PROTECTED]> wrote:
> This code causes IMCC to hang:
> ... This started happening around
> the time the 'multiple return' bug was
> fixed,
Seems to be related with the multiple freeing reported by Michael.
With the workaround it runs fine now.
leo
There are a number of ops that could fail. Examples are find_lex but
also the various load and lookup ops. Options for handling failure are:
- Abort parrot
- Throw an exception
- Return a default (null) value
I think it is hard for the parrot designers to decide what language
implementors want (g
Michal Wallace wrote:
Gosh you're quick. Thanks!
Welcome
Want another one? :)
Always.
def g():
return 0
def f():
return g()
print f()
This prints:
'No more I register frames to pop!'
The return continuation P1 in f() isnt preserved.
# f from line 3
.p
On Fri, 8 Aug 2003, TOGoS wrote:
> I want to be able to have a function with
> this kind of signature:
>
> func ($param1, *$otherparams)
>
> AFAIK, there is no way to implement this
> with the current calling conventions. You
> would have to do something with variable
> register IDs, which we do
> A test for seek and tell is added to t/pmc/io.t
>
> All tests pass for Linux/i386 and MacOS X (thanks Dan)
>
> Windows is untested but I hope i got the things right.
t/pmc/io...NOK 3# Failed test (t/pmc/io.t at line 37)
# got: 'fdopen failed
# '
# expected: 'ok
# '
t
Michal Wallace <[EMAIL PROTECTED]> writes:
> 1. Should there be a new_pad that takes
> no arguments to do this, so we don't
> have to keep count manually?
>
> 2. When would you NOT want to use
> new_pad (current_depth+1) ?
Remember, the pad depth reflects lexical scope nesting,
no
JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> Some refactoring in the seek/tell system.
Thanks, applied.
leo
> The current implementation of find_lex (by_name) is suboptimal. A linear
> scan over the list of lexical names is performed
> (s. sub.c:lexicals_get_position()).
>
> A better way would be to provide a list of lexicals plus a name hash,
> where hash values are indices into the list.
What would be
Well, it turns out that at least some compilers (AIX's) are really
unhappy about redefined #defines in the C source. This turns out to
be a problem with things like HAS_STDLIB_H, which is common enough to
cause collisions. So, we need to go name-prefix all the #defines.
So, the project. Someone
On Sat, 9 Aug 2003, Benjamin Goldberg wrote:
> Michal Wallace wrote:
> [snip]
> > def f():
> > return g()
> [snip]
> > # f from line 3
> > .pcc_sub _sub1 non_prototyped
> > .local object res1# (visitReturn:528)
> > find_lex $P2, 'g' # (callingExpress
Michal Wallace <[EMAIL PROTECTED]> wrote:
> The following code segfaults immediately.
Nasty multiple freeing the same symbol.
I've committed a würgaround.
Thanks for the bug report.
leo
On Sun, 10 Aug 2003, Leopold Toetsch wrote:
> Piers Cawley <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch <[EMAIL PROTECTED]> writes:
> >> As calling conventions clearly state, that the caller has to save
> >> everything, its probably up to imcc/pcc.c to insert above
> >> statements, if another su
> Puts #ifdefs as per the rest of i386/jit_emit.h.
Good land! How did he compute that? It works!!!
On Sun, 10 Aug 2003, Vladimir Lipskiy wrote:
> > Seems to be related with the multiple freeing reported by Michael.
>
> I thought his name was Michal (:>8
yes, I was born without an e. :)
Sincerely,
Michal J Wallace
Sabren Enterprises, Inc.
-
contact: [EMAI
At 11:06 AM +0200 8/8/03, Leopold Toetsch wrote:
This is an unordered list of issues - mainly design questions - about
the specific implementation of some parts.
Interpreter globals
---
We have real globals (e.g. Parrot_base_vtables, Env) and per
interpreter/thread globals (e.g. cla
Hello,
the correct fix is probably having different code paths for Win32 (because
on Windows NT/2000/XP/.Net and funnier names of the future environment
is/will be Unicode, not char*). For now this makes env.t pass on Win32.
Regards
Mattia
parrot.cvs.diff
Description: Binary data
Puts #ifdefs as per the rest of i386/jit_emit.h.
Regards
Mattia
Index: jit/i386/jit_emit.h
===
RCS file: /cvs/public/parrot/jit/i386/jit_emit.h,v
retrieving revision 1.79
diff -u -2 -r1.79 jit_emit.h
--- jit/i386/jit_emit.h
On Sun, 10 Aug 2003, Jim Cromie wrote:
> following corrects 1 remaining use of bare 'perl' to match all the other
> uses of $(PERL)
Thanks, applied.
Simon
On Thu, Aug 14, 2003 at 12:52:42PM +0100, Alberto Manuel Brandão Simões wrote:
> Apocalypses and Exegesis are not an 'official' specification for Perl6,
> I mean, they are subject to change. Is there any idea when will we have
> a freeze on the syntax and features for perl6?
Its scheduled to occur
--- TOGoS <[EMAIL PROTECTED]> wrote:
>
> Leopold Toetsch wrote:
> > TOGoS wrote:
> Unprototyped :-) I guess I didn't make that
> quite clear, enough.
> >>>
> >>> Setup a param array, that's all.
> >>>
> >>> leo
> >> Umm... OK. Here's what I've done: I created 2
> >> functions that I ca
following corrects 1 remaining use of bare 'perl' to match all the other
uses of $(PERL)
--- root.in~Sun Aug 10 15:54:44 2003
+++ root.inSun Aug 10 17:58:02 2003
@@ -480,7 +480,7 @@
cpu_dep$(O) : $(GENERAL_H_FILES)
nci.c : call_list.txt build_nativecall.pl
-perl build_nativecall.pl ca
Michael G Schwern wrote:
>
> On Mon, Aug 11, 2003 at 01:45:35AM -0700, Ask Bjoern Hansen wrote:
> > We totally need to have Parrot running on this thing when it comes
> > out. :-)
> >
> > http://www.xgamestation.com/
>
> Great idea, shame the hardware is crap. :(
>
> "Third-generation Motorol
Steve Fink <[EMAIL PROTECTED]> wrote:
> I want to know what people think of the state of things they're
> working on first.
PCC is still missing the return convention stuff (and unifying call and
return convention)
PackFile is in flux, but this need a lot more anyway.
> As for the version number
Michal Wallace <[EMAIL PROTECTED]> wrote:
> Could you serialize a parrot function?
> In other words, if you interactively define a
> function at the prompt, could you save it to
> disk? (not the source code, the actual binary
> representation of the function?)
Yes. Its almost done. It needs some
> that's mostly because there's no difference
> between set
> semantics and assign semantics for ints. You can
> think of them as both
> having assign semantics, if you like.
Works better to think of only 'set' semantics.
I think of it like this, and it makes things
work out very nicely:
Think o
- Original Message -
From: "Sean O'Rourke" <[EMAIL PROTECTED]>
To: "K Stol" <[EMAIL PROTECTED]>
Cc: "Michal Wallace" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 11, 2003 7:36 AM
Subject: Re: pirate status / need help with instances
> "K Stol" <[EMAIL PROTECTED]> writes:
On Mon, Aug 11, 2003 at 10:29:26AM +0100 it came to pass that Piers Cawley wrote:
> > Maybe this should be a global something...
>
> Not global. Or, if it is global, it needs to be dynamically scoped
> since you could possibly have different modules implemented in
> different languages.
After so
On Mon, 11 Aug 2003, Vladimir Lipskiy wrote:
>
> OK. I'm starting out a prefixing story and here is
> CHAPTER I. The HAS_HEADER_ defines.
>
Thanks, applied.
Simon
On Mon, 11 Aug 2003, Joseph F. Ryan wrote:
> How are you currently throwing/catching exceptions? I think it
> might be much more difficult to create a model that "traps"
> exceptions, rather than setting up code that just "figures out" how
> to handle an exception when it occurs. Both JVM->PIR a
Now EXEC works for ARM (linux) too.
- Original Message -
From: "Sean O'Rourke" <[EMAIL PROTECTED]>
To: "Michal Wallace" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, August 11, 2003 6:43 AM
Subject: Re: pirate status / need help with instances
> Michal Wallace <[EMAIL PROTECTED]> writes:
> > Py-pirate can now h
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23292]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23292 >
Hello,
It took me some minutes to find out how ARENA_DOD_FLAGS work. I added
a sectio
Fwd from Luke -- he's adopted a retarded MUA.
--- Luke Palmer <[EMAIL PROTECTED]> wrote:
> Date: Mon, 11 Aug 2003 21:22:05 -0600
> From: Luke Palmer <[EMAIL PROTECTED]>
> Subject: Re: Perl 6's for() signature
>
> Austin Hastings writes:
> > > And you can't do that because the loop has no way of k
Michal Wallace <[EMAIL PROTECTED]> wrote:
> Here's a new test case for t/pmc/sub.t
>
> output_is(<<'CODE', <<'OUTPUT', "set_eh - throw - clear_eh");
> print "start\n"
> newsub P20, .Exception_Handler, _handler
> set_eh P20
> new P30, .Exception
> throw P30
> prin
- Original Message -
From: "Piers Cawley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 11, 2003 5:42 AM
Subject: This Week's Summary
Perl 6 Summary for the week ending 20030810
Another week, another summary. How predict
TOGoS:
# syntax. As it is, the add(ints) op and the
# add(pmcs) ops do very different things (one
# has 'set' while the other has 'assign' semantics),
# but they look exactly the same. If not at
I think that's mostly because there's no difference between set
semantics and assign semantics for ints
Hi,
The long story short:
* EXCEPTION_LEX_NOT_FOUND is not picked up correctly from the include file
* The return continuation of the exception does not save registers,
since $P1 (mapped to P16 by imcc) is messed up by $P2 (also mapped to
P16).
* I would really like the name of the missing le
--- Luke Palmer <[EMAIL PROTECTED]>
wrote:
> TOGoS writes:
> > I0 Prototyped return?
> > I1 Number of overflow return values
> > I2 Number of return values in PMC registers
> > P3 Overflow return values in an array PMC
> >
> > so as to make call/return symmetrical
> > (this would also allow me
Comments welcome, Leon
About order of v-string:
It would be good in details results that 1.18 would be first before 1.2.
Eg:
1.18 (2 PASSes)
97757 PASS sun4-solaris
97976 PASS i586-linux
1.17 (1 FAIL)
97620 FAIL sun4-solaris
1.16 (1 FAIL)
97484 FAIL sun4-solaris
in place of
1.3 (3 PASSes)
22
Thus, I think that my website is correct in sorting the version
numbers. 1.2 should be later than 1.18. I think your versioning system
is wrong ;-)
Ok as this is not *my* versioning system, I will explain.
I use CVS, and extract version from something like:
$VERSION = ('$Revision: 1.18 $ ' =~ /(\d+
Bernhard Schmalhofer <[EMAIL PROTECTED]> writes:
> I have started an implementation of m4 in PIR.
The implications are staggering... Sure, plenty of
compilers can bootstrap themselves, but how many can
generate their own configure scripts via autoconf? With
p4rrot, we may live to see this dream.
TOGoS:
# When I say in IMCC:
#
# $P0 = $P1 + $P2
#
# , I expect it to create a new value and store it in
# $P0, not give me a segfault because I didn't say
#
# $P0 = new
#
# first.
Then your expectations are wrong.
I think you may be losing sight of the fact that most users will *never*
Graham Barr sent the following bits through the ether:
> > http://testers.cpan.org/search?request=dist&dist=MIME-Lite-HTML
> > keeps on timing out, so I don't know what it does. Graham?
>
> I just added a new index to the database. It should be much quicker now.
Wow, that's like a 100x speedup.
On Wednesday 13 August 2003 05:07, Leopold Toetsch wrote:
> I started extending the packfile functions towards multiple code
> segments. First is still some cleanup, but I already have troubles with
> the EXEC stuff :-(
I could not reproduce the error here.
> The debugger doesn't really like this
On Wed, 2003-08-13 at 17:20, Leon Brocard wrote:
> Graham Barr sent the following bits through the ether:
>
> > > http://testers.cpan.org/search?request=dist&dist=MIME-Lite-HTML
> > > keeps on timing out, so I don't know what it does. Graham?
> >
> > I just added a new index to the database. It s
According to the PDD03 I have here:
Calling conventions:
I0 Prototyped call?
I1 Number of overflow params
I2 Number of params in PMC registers
P3 Overflow params
Return conventions:
I0 Prototyped return?
I1 Number of return values in integer registers
I2 Number of return values in string r
On Tuesday, August 12, 2003, at 12:38 PM, Leon Brocard wrote:
We've used the Perl testing framework (Test::Harness, eg: 1..1\nok 1)
in the main parrot test suite. It's working well for Perl and a Parrot
version of it might be nice idea...
Anything that emits the Test::Harness protocol is fine. An
D:\build\parrot>nmake
[snip]
Microsoft (R) Library Manager Version 6.00.8168
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
rem blib/lib/libparrot_s.lib
link -out:parrot.exe -nologo -nodefaultlib -debug -pdb:none-machine:
x86 test_main.obj blib/lib/libparrot_s.lib
Here is s short overview of the current packfile changes til now
(PackFile-6).
- struct PackFile is now a PackFile_Directory holding BYTECODE,
CONSTANT, FIXUP and some other segments
- directories can have subdirectories which can be e.g. loaded packfiles
- ... which is done by the C opcode
- the
> Apocalypses and Exegesis are not an 'official' specification for Perl6,
> I mean, they are subject to change. Is there any idea when will we have
> a freeze on the syntax and features for perl6?
Since the A/E gig is where the design team is getting a handle on what it
is they want to be doing an
Togos <[EMAIL PROTECTED]> wrote:
> add(out PMC, in PMC, in PMC)
> add!(in PMC, in PMC, in PMC)
While that is all fine and useful, we would need that for e.g. keyed set
and get too (store/get a reference or value). So that would lead to
effectively almost doubling our opcode count.
This can l
Hi
Apocalypses and Exegesis are not an 'official' specification for Perl6,
I mean, they are subject to change. Is there any idea when will we have
a freeze on the syntax and features for perl6?
Thanks,
Alberto
The question is simple, and Dan can have the same problem (or him or
Larry). I am thinking on a Perl 6 book in portuguese (maybe only a
tutorial... but who knows). But that means I must write something which
will work :-)
Of course to write it will take many time, which can give Larry time to
writ
On Thu, 2003-08-14 at 14:49, Simon Cozens wrote:
> [EMAIL PROTECTED] (Alberto Manuel Brandão simões) writes:
> > The question is simple, and Dan can have the same problem (or him or
> > Larry). I am thinking on a Perl 6 book in portuguese (maybe only a
> > tutorial... but who knows). But that means
--- Brent Dax <[EMAIL PROTECTED]> wrote:
> TOGoS:
> # When I say in IMCC:
> #
> # $P0 = $P1 + $P2
> #
> # , I expect it to create a new value and store it
> in
> # $P0, not give me a segfault because I didn't say
> #
> # $P0 = new # $P0 is supposed to be based
> #
* Jonathan Scott Duff ([EMAIL PROTECTED]) [15 Aug 2003 00:16]:
[...]
> Besides you could always provide online updates to your book as the
> language changes. The first (dead tree) edition would be the rough
> cut, and later editions would be closer to reality as the language
> stablizes.
Much li
On Fri, Aug 15, 2003 at 12:19:28AM +1000, Iain Truskett wrote:
> * Jonathan Scott Duff ([EMAIL PROTECTED]) [15 Aug 2003 00:16]:
>
> [...]
> > Besides you could always provide online updates to your book as the
> > language changes. The first (dead tree) edition would be the rough
> > cut, and late
On Mon, Aug 11, 2003 at 01:45:35AM -0700, Ask Bjoern Hansen wrote:
> We totally need to have Parrot running on this thing when it comes
> out. :-)
>
> http://www.xgamestation.com/
Great idea, shame the hardware is crap. :(
"Third-generation Motorola 68HCS12 16-bit processor @ 25 MHz.
Graphic
add(out INT, in INT, in INT)
add(out NUM, in NUM, in INT)
add(out NUM, in NUM, in NUM)
add(in PMC, in PMC, in INT)
add(in PMC, in PMC, in NUM)
add(in PMC, in PMC, in PMC)
This kind of ties into the 'set vs assign' issue.
Add behaves differently depending on whether
the first parameter is an intege
Bernhard Schmalhofer sent the following bits through the ether:
> Is there already a testing framework in PIR or PASM? For now I've just
> tweaked the Makefile from bf.
This looks excellent.
First, may I be the first to say that I'm happy that BF is the
inspiration for so many Parrot projects ;
Hi,
I have started an implementation of m4 in PIR. See
http://www.gnu.org/software/m4/m4.html.
Initially I wanted to tackle Ruby or QCL,
http://tph.tuwien.ac.at/~oemer/qcl.html. But I found those too intimidating.
The goal is to make a lot of tests work, and eventually getting a drop
in repla
On 11 Aug 2003, Juergen Boemmels wrote:
> Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> > At 11:48 PM +0200 8/5/03, Leopold Toetsch wrote:
> > >Simon Glover wrote:
> > >
>
> parrot_compiler: No make test:
> make fails with missing 'open_i_s' (integer file descriptors
> are remo
It fails here:
system("$link $linkflags test$o ${cc_exe_out}test$exe $libs >test.ldo
$redir_err") and die "Linker failed (see test.ldo)";
Most likely one of the variables($link, $linkflags and so forth) isn't set
up or is set up incorrectly by this step.
Therefore, could you send me a dump of yo
- Original Message -
From: "Jonathan Worthington" <[EMAIL PROTECTED]>
To: "K Stol" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, August 10, 2003 6:08 AM
Subject: Re: configure.pl failed under cygwin, build failed on win32
> Hi,
>
> > I just picked up a fresh copy with cvs.
> > U
On Tue, 12 Aug 2003, Jürgen Bömmels wrote:
> It took me some minutes to find out how ARENA_DOD_FLAGS work. I added
> a section to memory_internals.pod that others hopefully need a few
> minutes less to figure out what its good for.
>
Thanks, applied, with a few tweaks.
Simon
> So, the project. Someone needs to go through the configure procedure
> and the headers and throw a PARROT_ prefix in front of all the HAS_
> defines we define, so we can avoid this problem.
I have a look at the configure procedure and didn't find anything that
could have set up something like HA
Hey all,
Sorry for the huge code listing here, but I don't
have a simpler case. This is what pirate outputs
when it compiles the following program:
def f(x):
if x:
return 1
else:
return 0
print f(1), f(0)
As far as I can tell,
I wrote:
> >While configuring we generate 3 header files: config.h, has_header.h,
> >feature.h.
Plus I forgot to mention of specific cc flags like -DHAS_JIT, -D$jitcpuarch,
-DHAVE_COMPUTED_GOTO, -DGC_IS_MALLOC which we set up
in jit.pl, cgoto.pl, gc.pl respectively. I think the flags could settle
When the Perl 6 book came out last month, I contacted the authors
because they use a "vector operator", >>+<<, rather than hyper-operator
^. Allison Randall replied:
"The name and the representation changed late last year in
a big operator cleanup, but the functionality is the same."
So what i
On Tue, 12 Aug 2003, Leopold Toetsch wrote:
> > ... So I'm trying to decide between two
> > approaches:
>
> 3) wait until classes and objects are done ;-)
4) simulate an object system with closures :)
I wound up getting a couple C books today. I'm
trying to see what I can do about wrapping
PyO
TOGoS writes:
> I0 Prototyped return?
> I1 Number of overflow return values
> I2 Number of return values in PMC registers
> P3 Overflow return values in an array PMC
>
> so as to make call/return symmetrical
> (this would also allow me to use the same
> Params class in my compiler for both
> c
Luke Palmer <[EMAIL PROTECTED]> writes:
> Yes, it's possible to have two routines with the same name which
> differ by signature... however, in Perl 6, C has only one
> signature, and it's the one above. The C loop you are thinking
> of is spelled C,
Oh, yes, forgot about that.
> To the cont
Index: config/gen/makefiles/root.in
===
RCS file: /cvs/public/parrot/config/gen/makefiles/root.in,v
retrieving revision 1.104
diff -u -r1.104 root.in
--- config/gen/makefiles/root.in 12 Aug 2003 07:57:33 - 1.104
+++ config/gen/make
I've checked in a first attempt towards resumable exceptions thrown at
opcode level. s. t/op/hacks_4 for an example.
As such ops have to be marked as branches, I did extend OpsFile.pm to
understand:
restart ADDRESS(resume);
This marks such opcode as branches. s. var.ops: find_lex_p_s.
inter
>This only happens on Windows. On Linux i can build pdb and step
>through the pasm code. This smells like makefile problems. Can you try
>the attached patch?
WORKS! I'm out of English words; I just run mandel.pbc in pdb
and it printed out such a cool Mandel bug or whatever(or maybe
even Leon Broca
* Leon Brocard ([EMAIL PROTECTED]) [13 Aug 2003 21:31]:
[...]
> Thus, I think that my website is correct in sorting the version
> numbers. 1.2 should be later than 1.18. I think your versioning system
> is wrong ;-)
Which is the correct response. Versions should be flaots.
> http://dellah.org/te
On Tue, 12 Aug 2003, Leopold Toetsch wrote:
> Juergen Boemmels <[EMAIL PROTECTED]> wrote:
>
> > what still fails is pbc2c.pl (This needs Parrot::Packfile, which can
> > only read format 0 (old assemble.pl) bytecodes).
>
> This is obsoleted by Daniel's exec patches.
Don't we need to keep this fo
Leopold Toetsch wrote:
> TOGoS wrote:
Unprototyped :-) I guess I didn't make that
quite clear, enough.
>>>
>>> Setup a param array, that's all.
>>>
>>> leo
>> Umm... OK. Here's what I've done: I created 2
>> functions that I can use when dealing
>> with variable-length parameter lists.
- Original Message -
From: "Brent Dax" <[EMAIL PROTECTED]>
To: "'TOGoS'" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 13, 2003 11:25 PM
Subject: RE: set vs. assign, continued: 'add' vs. 'add!'
> TOGoS:
> # syntax. As it is, the add(ints) op and the
> # add(pmcs) op
On Wed, 2003-08-13 at 19:06, Leon Brocard wrote:
> Graham Barr sent the following bits through the ether:
>
> > > Now maybe I should ignore the version numbers and instead sort using
> > > the dates that the module was uploaded to CPAN, but that's external
> > > information, bah.
> >
> > That is
Dan Sugalski wrote:
>
> At 11:06 AM +0200 8/8/03, Leopold Toetsch wrote:
[snip]
> >PMC methods
> >---
> >ParrotIO has methods via find_method/invoke. Should that be a general
> >mechanism in default.pmc with one vtable slot for the meth hash?
>
> We're going to want lexially nested method
Andy Bussey <[EMAIL PROTECTED]> wrote:
> There appears to be a problem whereby numbers that include
> decimal points inside IMCC POD cause an error. E.g.:
Ah, yes thanks (the default rule wan't greedy).
Fixed.
leo
1 - 100 of 247 matches
Mail list logo
