Matt Fowles wrote:
LuaNil Morphing
Klaas-Jan Stol proffered a patch which changed LuaNil from a singleton
and made it morph to other Lua types when asked. Warnock applies.
Actually, François Perrad applied this patch, but I think he only sent a
reply to me.
http://xrl.us/jpww
From: Matt Fowles [EMAIL PROTECTED]
Date: Tue, 24 Jan 2006 21:50:47 -0500
Perl 6 Summary for 2006-01-10 though 2006-01-24
Perl 6 Internals
Clean Up After Yourself
Bob Rogers provided a patch which makes examples/pir/io.pir clean up
its temp file. Warnock
A bunch of namespace opcodes and methods could work absolute or
relative. E.g.
$P0 = get_namespace [Foo; Bar]
Where should the lookup start?
Is this to be considered absolute (from namespace root), absolute from
the current HLL setting, or relative from the current namespace?
Thanks,
leo
Bob Rogers wrote:
Sometime between r11268 (probably) and 11276, there was a change to
the way that initialization methods get called, regardless of whether
__init or a 'BUILD' property is used. If I do
.local pmc foo, hash
.local int foo_class
foo_class = find_type
Brad Bowman (via RT) wrote:
Looking through pobj.h, I found what seems to be a dated
comment referring to cache.*. I don't think this exists
anymore, unless it's referring to hashval in some oblique way.
Sorry for the delay, I must have missed it. Anyway, your observations
are correct,
Brad Bowman (via RT) wrote:
-=item CParrot_call(interp, Parrot_PMC sub, Parrot_Int argcount, ...)
+=item CParrot_call_sub(interp, Parrot_PMC sub, Parrot_Int argcount, ...)
This still doesn't reflect src/extend.c usage. But don't worry too much
about pdds/clip/* - these are being reworked.
Having it be absolute makes more sense to me, but there likely will be
people who want relative. Maybe something like:
$P0 = get_namespace[;Foo;Bar]
Where the empty part mean current namespace here. Of course, then
it'd be really confusing because it's the opposite of pathnames on
Leopold Toetsch [EMAIL PROTECTED] wrote:
A bunch of namespace opcodes and methods could work absolute or
relative. E.g.
$P0 = get_namespace [Foo; Bar]
Where should the lookup start?
Absolute. If people want relative lookups, I'd consider adding another opcode:
$P1 = get_namespace #
On Tue, Jan 24, 2006 at 12:34:28PM -0800, Chip Salzenberg wrote:
add_scalar(STRING, PMC*)
add_array(STRING, PMC*)
add_hash(STRING, PMC*)
WRT namespaces, I'm starting to think we should replace each *_var()
functions with three functions *_scalar(), *_array(), and *_hash(). Parrot
Already checked, it's not linked to.
Any missing docs on the website, please open a fresh ticket.
Regards.
On Jan 25, 2006, at 10:08 AM, Bernhard Schmalhofer via RT wrote:
jisom did most of the renaming in r11180.
I renamed README.win32 in r11351.
So it looks like everything is taken care
On Tue, Jan 24, 2006 at 09:19:48AM -0800, Larry Wall wrote:
On Tue, Jan 24, 2006 at 01:04:10PM -, Jonathan Worthington wrote:
: Looking at what Chip said though, it would appear that the much cleaner
: solution I was hoping to find exists and can be found in lex pad stuff,
: which I need
On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
*) what is Stash.parent_stash? (It's currently unused)
Historically, stash is perl5-guts-speak for namespace. However, I see
in Parrot the Stash structure which seems quite different. From its usage,
I gather it's an attempt at
Hi
After some discussion on #parrot, and after Leo direct me to this link:
http://mail.python.org/pipermail/python-dev/2006-January/060026.html
Follows some discussion on File.pmc.
1) What it is now.
At the moment we have two OS dependent PMCs: OS and File.
OS includes stat, mkdir, remove,
On Wed, Jan 25, 2006 at 09:10:50PM +, Alberto Simões wrote:
2) What it might be.
My first idea is to join both PMCs, and create a FileSystem PMC. The
main problem is its name. After looking to Python discussion, and
thinking a little on the PIR syntax, I would call it Path.
3)
Nicholas Clark wrote:
Is your implementation going to cope with one OS having several different
types of file systems mounted, that might have different specific behaviours?
I know that HFS+, ufs and ext3 all have various forms of flags/extended
attributes, and in turn I'd assume that a
Without -yet- commenting on the File/OS/Filesystem issue, this bit of code
is either substantially wrong or just a convenience wrapper around what's
really going on:
On Wed, Jan 25, 2006 at 09:10:50PM +, Alberto Simões wrote:
$P0 = new .Path(/foo/bar)
[...]
$P0.is_dir()
It is necessary that Parrot's filesystem interface make user-visible the
_event_ of measuring the attributes of a path _or_ an already open
filesystem object (e.g. calling stat() or fstat()). It must also represent
the bundle of measurements returned as some kind of PMC. (handwave handwave)
I
On Wed, Jan 25, 2006 at 10:24:51PM +, Alberto Simões wrote:
Chip:
The above-quoted example is only plausible if it's shorthand for, e.g.:
$P1 = $P0.stat # or lstat
$P1.is_dir()
$P1.is_file()
Looking to this code, $P0.stat should return a Stat PMC object, so we
can
On Jan 25, 2006, at 21:21, Chip Salzenberg wrote:
On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
*) what is vtable-package? A pointer to the namespace PMC of this
class? (It's currently unused)
Beats me. Vtables don't have namespaces. Pleaes just comment it as
WTF?
From: Leopold Toetsch [EMAIL PROTECTED]
Date: Wed, 25 Jan 2006 16:54:59 +0100
Bob Rogers wrote:
Sometime between r11268 (probably) and 11276, there was a change to
the way that initialization methods get called, regardless of whether
__init or a 'BUILD' property is used.
On Thu, Jan 26, 2006 at 02:12:41AM +0100, Leopold Toetsch wrote:
On Jan 25, 2006, at 21:21, Chip Salzenberg wrote:
On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
*) what is vtable-package? A pointer to the namespace PMC of this
class? (It's currently unused)
Beats me.
Hi People,
Back in December I asked a question about utf8 I/O. Leo responded
pointing me at the encoding filters. I then published a possible
implementation of PIO_utf8_read with a request for comments.
Since that time I have been thinking about the testing and
implementation of I/O filters.
22 matches
Mail list logo
