On Nov-21, Dan Sugalski wrote:
>
> I was mostly thinking that some step or other in the Makefile has a
> dependency on that file, and some other step creates it, but the
> dependency's not explicit. I'd like to find the step(s) that require it
> and make it a dependency for them, then add in a dep
On Nov-21, Leopold Toetsch wrote:
> Steve Fink <[EMAIL PROTECTED]> wrote:
> > I'm staring at a crash
>
> > I'll attach the 5KB compressed .imc file (25KB uncompressed; PIR code
>
> Its really good, to have such short code snippets, that clearly show,
> where a bug is coming from ;) Anyway, it was
> A clean running make not cluttered with tons of warnings gives a more
> confidental feeling for the quality of the project and just looks
> better.
In the spirit of this, I attach a couple of patches that clear up some of
the many warnings on Win32. One of them is the long standing problem of
mi
Almost forgotten about that, but I've checked in some days ago the base
of Hash randomization, which is basically most of a ?rand48 library.
I don't know if its useful or practically usable with HLL code
generation but I've added to these randon function interface a
how_random parameter, which
On Fri, 21 Nov 2003, Harry wrote:
> --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > Should be straightforward though it involves diving into a twisty
> > maze of
> > make rules, so maybe not. Anyway, trying a "make -j 4" dies a quick
> > and
> > horrible death, failing to find Parrot/OpLib/core.pm
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> 5) The vtable API
[ ... ]
> thawfinish()
This is very probably necessary to perform some final state adjustemnt,
when all the contained PMCs are done but not as a general "to be
called on each". E.g. a plain scalar PMC doesn't need it. I'd rather
have s
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Should be straightforward though it involves diving into a twisty
> maze of
> make rules, so maybe not. Anyway, trying a "make -j 4" dies a quick
> and
> horrible death, failing to find Parrot/OpLib/core.pm. My assumption
> here
> is that we're just mis
These could use some documenting (and yes, I know the answer to many) for
future use for folks generating PIR. (Hint, hint -- documentation is a
good thing)
*) How do I declare an externally visible subroutine?
*) How do I store a global variable
*) How do I load a global variable
*) How do I c
The beginnings of freezing and thawing are going in, which is good -- this
should get us to PMC constants in the bytecode files, and proper
over-the-wire freeze/thaw stuff. We're a bit raw at the moment, which is
fine, so I wanted to give a heads up as to where things are moving, what
needs doing,
Should be straightforward though it involves diving into a twisty maze of
make rules, so maybe not. Anyway, trying a "make -j 4" dies a quick and
horrible death, failing to find Parrot/OpLib/core.pm. My assumption here
is that we're just missing some dependency rules, as a make -j 2, or a
make -j 4
At 12:10 PM 11/21/2003 +0100, Leopold Toetsch wrote:
Robin Redeker <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Robin,
> Currently i would like to target parrot for some language experiments.
> But i wonder which parts of parrot are stable enough and which
> part of the IMCC language is finished and wont c
Robin Redeker <[EMAIL PROTECTED]> wrote:
> Hi,
Welcome
> Currently i would like to target parrot for some language experiments.
> But i wonder which parts of parrot are stable enough and which
> part of the IMCC language is finished and wont change much in future?
Existing syntax will not change
Steve Fink <[EMAIL PROTECTED]> wrote:
> I'm staring at a crash
> I'll attach the 5KB compressed .imc file (25KB uncompressed; PIR code
Its really good, to have such short code snippets, that clearly show,
where a bug is coming from ;) Anyway, it was again me causing this bug -
sorry.
Fixed and u
Hi,
i don't know whether this list is the right list to ask this question:
I have been following the parrot (and perl6) development (mailing lists)
for some time now, and i can't wait to play around with parrot.
Currently i would like to target parrot for some language experiments.
But i wonder wh
I'm staring at a crash, my eyes are glazing over, and I need sleep. So
I was wondering if anyone would be interested in taking a look at a
.imc file that is giving me a seg fault while marking a hash in a gc
run triggered by a hash PMC allocation. Or at least tell me whether
it's seg faulting on yo
15 matches
Mail list logo
