Jonathan Worthington:
> work something out. :-) However, Brent said "If you mean precompiled
> binaries, not yet. Parrot is still under development, so we aren't
shipping
> binaries.", so I'm guessing maybe I shouldn't do a ZIP with the
executables
> in? But in that case I guess there's no poin
At 11:37 PM 8/4/2003 -0400, Brent Dax wrote:
Jonathan Worthington:
> work something out. :-) However, Brent said "If you mean precompiled
> binaries, not yet. Parrot is still under development, so we aren't
shipping
> binaries.", so I'm guessing maybe I shouldn't do a ZIP with the
executables
>
"Jonathan Worthington" <[EMAIL PROTECTED]> writes:
> work something out. :-) However, Brent said "If you mean
> precompiled binaries, not yet. Parrot is still under development,
> so we aren't shipping binaries.",
This doesn't make sense to me. People who don't like hacking C can
still use a pr
Hi,
> Tuesday, August 5, 2003, 12:28:16 AM, you wrote:
>
> JW> What needs to go into the ZIP? My guesses are:-
> JW> - parrot executable
> JW> - imcc executable
> JW> - The docs directory
> JW> - The examples directory
> JW> - The languages directory
> JW> If you want regular
Hello Jonathan,
Tuesday, August 5, 2003, 12:28:16 AM, you wrote:
JW> I can most probably do this; I've got the latest CVS checkout compiled here.
JW> What needs to go into the ZIP? My guesses are:-
JW> - parrot executable
JW> - imcc executable
JW> - The docs directory
JW> - The e
Hello Brent and others,
BD> If you mean precompiled binaries, not yet. Parrot is still under
BD> development, so we aren't shipping binaries.
OK, clear.
well, what about win32 milestones?
BD> The list is named "perl6-internals" mostly for historical reasons--the
BD> discussion on it is almost e
Hello Dan and ALL,
Monday, August 4, 2003, 11:44:11 PM, you wrote:
DS> Not that I know of. If someone's got a working build and can put
DS> together a tarball or zip file, we can get it up for download.
nice. ... but sounds, strange for me as for newbie :-)
win32 is a platform and there should b
- Original Message -
From: "Dan Sugalski" <[EMAIL PROTECTED]>
To: "Valery A.Khamenya" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 04, 2003 10:44 PM
Subject: Re: parrot, win32, stand-alone distribution, separate Parrot
maillist
> At 8:48 PM +0200 8/4/03, Valery A.Khamenya
Valery A.Khamenya:
> are there any info on getting ready-to-try
> Parrot for win32 as stand-alone distribution?
If you mean precompiled binaries, not yet. Parrot is still under
development, so we aren't shipping binaries.
> What about separate Parrot maillist?
> (I am really sorry, I am
At 8:48 PM +0200 8/4/03, Valery A.Khamenya wrote:
Hi All,
are there any info on getting ready-to-try
Parrot for win32 as stand-alone distribution?
Not that I know of. If someone's got a working build and can put
together a tarball or zip file, we can get it up for download.
What about sepa
Hi All,
are there any info on getting ready-to-try
Parrot for win32 as stand-alone distribution?
If win32 is not met yet, what are the milestones then?
What about separate Parrot maillist?
(I am really sorry, I am not interested in Perl,
but in Parrot)
thanks a lot.
--
Valery
At 11:05 PM +0300 8/4/03, Vladimir Lipskiy wrote:
I don't think I was reading pdd03_calling_conventions.pod
in a slipshod manner and I swear that this place in the pod
=item I1
The number of items pushed onto the parameter list.
is the personification of confusion.
Then I'll go clarify that. :)
-
I don't think I was reading pdd03_calling_conventions.pod
in a slipshod manner and I swear that this place in the pod
>=item I1
>
>The number of items pushed onto the parameter list.
is the personification of confusion.
> I1 ... Number of items in the overflow/parameter array P3.
Hell yeah. Tha
Having applied a bit more thought, having the generation field as part
of the PMC isn't all that great -- it makes PMCs larger, but it's really
only needed for new/neonate pmcs.
Instead of attatching the generation directly to the pmc, have a global
(per-interpreter) stack of neonate pmcs. Each
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > I was recently reading the following:
> >
> >http://www.parrotcode.org/docs/dev/infant.dev.html
> >
> > It's missing some things. One of which is the (currently used?) way
> > of preventing infant mortality: anch
At 12:03 AM -0400 8/4/03, Michal Wallace wrote:
nd in the PMC vtable, it maps this way:
in = get_*_keyed, set_*_keyed, delete_keyed_*
on = getprop / setprop / delprop
Is that right?
For Python, yep.
the _keyed stuff is for access to container things--hashes and
arrays, generally, though anyt
Thanks, applied (with a few typographical tweaks by me).
Simon
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #23218]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23218 >
Recent mailing list discussions added some new variants to the infant
mortality proble
> --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > At 11:45 AM -0700 8/1/03, TOGoS wrote:
> > > ...blah, blah, blah...
> > >
> > > What I don't like about this is
> > > that it's not immediately obvious
> > > from looking at the code whether
> > > you're telling P3 to change its
> > > value or simpl
Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
>> > foo($var1, $var2, $var3, ... , $var23);
>>
>> I would expect I2=11, I1=12
> D'oh, I suspected it should be I2=11, I1=23.
No. You have the first 11 parameters in P5..P15 (I2=11). Then you have 12
more, which go into the overflow array P3 (I1=12)
>
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 11:45 AM -0700 8/1/03, TOGoS wrote:
> > ...blah, blah, blah...
> >
> > What I don't like about this is
> > that it's not immediately obvious
> > from looking at the code whether
> > you're telling P3 to change its
> > value or simply replace the PMC
Here's some stuff we need to add to the packfile format and the sub
header to get things ready for more language work.
Packfiles need to have a symbol table. A series of name/type/location
tuples so we can have global names that map to values in the
bytecode, either variables or subroutines. Wh
I'm digging out from under near two-weeks of p6i mail, and taking it
from back to front. If there are pending issues I've not gotten to in
the next few days (as it's a lunch and evening project) then pop them
back to the list and we'll get them addressed.
--
At 11:45 AM -0700 8/1/03, T.O.G. of Spookware wrote:
Hi, all. I've been following Parrot development and
been playing with Parrot for a...bout a year and a
half, now. First time posting to the list, though, so
forgive me if this has already been covered or is
stupid in some way :-)
Anyway, while pl
At 10:00 AM -0600 8/3/03, Luke Palmer wrote:
Is this supposed to happen?
% parrot -
.sub _main
$S0 = "Hello\n"
$S1 = $S0
substr $S1, 2, 2, ""
print $S0
print $S1
end
.end
(EOF)
Heo
Heo
Aren't strings supposed to follow value s
At 4:23 AM +0300 8/4/03, Vladimir Lipskiy wrote:
Q1: Suppose I have the following call into a sub named "foo":
foo($var1, $var2, $var3);
What should I set in I1? Is it 3?
Nope. I2 should be 3, and I1 0. (Assuming you put those three
parameters in the first three PMC registers, which is what you
At 3:28 PM +0200 8/4/03, Juergen Boemmels wrote:
I have the feeling that extending the signature of all
Parrot-functions will remove the need of walking the C-Stack
entirely. If this will be the linked list of frames or the generation
count is more or less a matter of taste: The generation count fo
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> I was recently reading the following:
>
>http://www.parrotcode.org/docs/dev/infant.dev.html
>
> It's missing some things. One of which is the (currently used?) way of
> preventing infant mortality: anchor right away, or else turn off DoD
> unt
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> Considering that parrot is now emitting an executable (on some
> platforms)... and IIRC, C will be one of the languages we plan to have
> parrot support for... will parrot be able to compile itself? :)
Not yet ;-)
There are some problems:
The emitte
> First of all, are you targeting PASM or PIR? For the latter, its done
> automatically.
I mean PASM
> > Q2: I'm calling without prototyping
>
> > foo($var1, $var2, $var3, ... , $var23);
>
> > Here, what should I place in I2? Is it 11 (as we have P5-P15) or
> > 23 (considering the P3 register)
Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> Q1: Suppose I have the following call into a sub named "foo":
First of all, are you targeting PASM or PIR? For the latter, its done
automatically.
> foo($var1, $var2, $var3);
> foo($var1, @arr2, %hash3);
> Is it still 3, since these aren't gonna be f
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> To what does 'bufused' refer? The number of bytes from where to where?
Number of bytes from strstart to "strend".
> I *thought* that it was from bufstart to the end of the string... no?
No, bufstart is the physical buffer start used for reallocati
32 matches
Mail list logo
