# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19031]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19031 >
Thanks to bf's example, I'm now writing Befunge Makefile while
configuring Parrot. I h
The Perl 6 Summary for the week ending 20021208
Another Monday evening. Another summary to write.
Starting, as is becoming tediously predictable, with perl6-internals.
Another JIT discussion
Toward the end of the previous week, Leopold Tötsch posted something
about the latest ro
Changes #6.
- PMC_*_FLAGs are history.
- I did remove the bogus looking, unused, untested and superfluous
from core.ops
All access to PMC/Buffer->flags has to be done via the accessor macros
in pobj.h. If some are missing, please add them, when needed.
Next will be hiding other Buffer/PMC str
I'm still not sure what the problem is...but if you turn --gc-debug off,
then the
array diminsions are correct...e.g., 10 for the first dimension. Therefore,
the calculation
of the array index is performed correctly. However, with --gc-debug on, the
array dimension
is correct for the first dimens
Done.
Buffers and PMCs are Parrot Objects now, sharing a common header, PObj.
The struct members:
- buffer
- buflen
- cache
- version (for GC_DEBUG)
are actually #defines now. This implies that the usage of these names is
forbidden in the whole parrot tree.
This rule will last until the final s
On Tue, Dec 10, 2002 at 06:04:44PM +, Piers Cawley wrote:
> Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> > At 4:45 PM + 12/5/02, Leon Brocard wrote:
> >>Leon Brocard sent the following bits through the ether:
> >>Ah, well, I gave up on SDL as it was a little complicated. Instead, I
> >>p
[EMAIL PROTECTED] wrote:
Leo --
I tried my hand at adding a naiive (that is, incorrect) version of
.const =
I'll implement such a thing based on your patch and on the recent
lexical changes. Constants declared like above will be real constants
without register usage.
Syntax will be
On Tue, 10 Dec 2002, Tanton Gibbs wrote:
> I'm looking at the Tru64 problem.
>
> The manifest problem is trivial:
> languages/jako/docs/jako.pod needs to be added to the MANIFEST
Implicit patch applied, thanks.
Simon
Dan --
We were talking earlier about Jako supporting native calls. I have looked
at PDD 6 and PDD 3, and here's what I think so far...
I don't think I can get the native call stuff working until I have IMCC
support
for PDD 3. IMCC is totally in charge of what goes into each register, and
I
like
Are in. You can now get, set, delete, and get a hash of PMC
properties. (Hopefully)
Alas, no tests. Working on that, but if someone wants to beat me to
it, feel free.
--
Dan
--"it's like this"---
Dan Sug
On Wed, 11 Dec 2002, Dan Sugalski wrote:
> Are in. You can now get, set, delete, and get a hash of PMC
> properties. (Hopefully)
>
> Alas, no tests. Working on that, but if someone wants to beat me to
> it, feel free.
I would expect this:
new P0, .PerlInt
new P1, .PerlInt
On Wed, 11 Dec 2002, Simon Glover wrote:
>
> Is this a bug, or am I misunderstanding how properties are supposed to
> work?
Well, there's definitely a bug somewhere, as the previously posted
example causes a segfault if run with --gc-debug. Backtrace follows:
#0 0x08075bb1 in hash_lookup (i
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #19059]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19059 >
Attached, please find a patch that makes jako's makefile slightly more
portable. I
On Dec-10, Tanton Gibbs wrote:
> I'm looking at the Tru64 problem.
Yay! Thank you.
On Dec-11, Tanton Gibbs wrote:
> I'm still not sure what the problem is...but if you turn --gc-debug
> off, then the array diminsions are correct...e.g., 10 for the first
> dimension. Therefore, the calculation of the array index is
> performed correctly. However, with --gc-debug on, the array
> di
15 matches
Mail list logo