Jens Rieks [EMAIL PROTECTED] wrote:
get_string() not implemented in class 'SArray'
I've gone through err3 and err4 and found a couple of flaws, which should
mostly be fixed now:
- method subs got compiled as non-prototyped
- namespace resetting to main wasn't really working
(now the namespace
Dan Sugalski [EMAIL PROTECTED] wrote:
Sure. Or we could make it:
.pcc_begin
.arg x
.object y
.meth_call foo
.result r
.pcc_end
Done. modulo s/\.object/.invocant/
leo
I promise I will learn hwo to use my email program. This should have
gone to the mailing list :-/
Dan Sugalski wrote:
At 10:22 PM + 3/12/04, Mark Sparshatt wrote:
Hi,
I've been reading PDD15. It seems that if the object foo is an
instance of the class Foo then foo is a ParrotObject pmc
This is another message that should have gone to the list :-[
Karl Brodowsky wrote:
Mark Sparshatt wrote:
From the description in PDD15 I'm not sure how to hand languages
where a class is also an object. Where Foo is an instance of Foo'
which is an instance of Class.
Could this be handled
Hi,
On Saturday 13 March 2004 07:28, Leopold Toetsch wrote:
Jens Rieks [EMAIL PROTECTED] wrote:
Hi,
.namespace [Source]
.sub open method
.pcc_begin_return
.pcc_end_return
.end
fails with
error:imcc:parse error, unexpected PARROT_OP, expecting IDENTIFIER
Parrot opcode names
Hi,
On Saturday 13 March 2004 09:41, Leopold Toetsch wrote:
Jens Rieks [EMAIL PROTECTED] wrote:
get_string() not implemented in class 'SArray'
I've gone through err3 and err4 and found a couple of flaws, which should
mostly be fixed now:
- method subs got compiled as non-prototyped
-
Mark Sparshatt wrote:
The problem is what happens when some Python code tries to call a class
method on a Ruby object? if Python doesn't know about the hidden
reference within Foo it won't be able to find Foo' in order to call the
method.
The issue you are addressing is finding the applicable
Karl Brodowsky wrote:
Mark Sparshatt wrote:
The problem is what happens when some Python code tries to call a class
method on a Ruby object? if Python doesn't know about the hidden
reference within Foo it won't be able to find Foo' in order to call the
method.
The issue you are addressing is
Jens Rieks [EMAIL PROTECTED] wrote:
$ tar xzf err5.tgz
$ cd err5
$ ../parrot main.imc
calling source.open( name, )...
segmentation fault
The interpreter is toatally messed up after the longjmp. I'll look
further what's happening here.
jens
leo
Mark Sparshatt wrote:
The problem is what happens when some Python code tries to call a class
method on a Ruby object? if Python doesn't know about the hidden
reference within Foo it won't be able to find Foo' in order to call the
method.
If I understand correctly, the Ruby object, as represented
So, if I understand this right (and I may well not), when you
instantiate a metaclass you get a class, and when you instantiate a
class you get an object, and since anything you instantiate is an
object anyway that means classes are objects. I'm not entirely sure
if metaclasses are objects,
Brent Dax Royal-Gordon wrote:
Mark Sparshatt wrote:
The problem is what happens when some Python code tries to call a class
method on a Ruby object? if Python doesn't know about the hidden
reference within Foo it won't be able to find Foo' in order to call the
method.
If I understand
Dan Sugalski wrote:
So, if I understand this right (and I may well not), when you
instantiate a metaclass you get a class, and when you instantiate a
class you get an object, and since anything you instantiate is an
object anyway that means classes are objects. I'm not entirely sure if
Dan Sugalski [EMAIL PROTECTED] wrote:
The one question I have is whether we need to have a call class
method operation that, when you invoke it, looks up the class of the
object and redispatches to it, or whether class methods are just
methods called on class objects.
The terms are
Jens Rieks [EMAIL PROTECTED] wrote:
$ tar xzf err5.tgz
$ cd err5
$ ../parrot main.imc
calling source.open( name, )...
segmentation fault
I'be now turned off the stacked exceptions (one per entering the
runloop) OTOH that seems to be needed for t/src/extend_13 - so I've
disabled that too.
On Mar-12, Leopold Toetsch wrote:
Steve Fink [EMAIL PROTECTED] wrote:
The attached patch should remove all of the conflicts, and replace
them with a single shift/reduce conflict that appears to be a bug in
the actual grammar, namely:
x = x . x
Ah yes. Or course, Thanks a lot,
At 9:06 PM +0100 3/13/04, Oli wrote:
Dan Sugalski wrote:
As well as involving much finding of instances, and moving of
their attribute
values, this isn't thread safe (please excuse my lack of PASM syntax
knowledge):
Yeah, adding an attribute requires a stop-the-world action, as
every object
But how should the two interpretations of x.x be resolved? Is that
concatenation or method calling?
currently, the pir line
S5 = S5 . 'foo'
produces
error:imcc:object isn't a PMC
concatenation with . seems to be gone
i cannot think of a good replacement for it
wouldnt it be better
luka frelih writes:
But how should the two interpretations of x.x be resolved? Is that
concatenation or method calling?
currently, the pir line
S5 = S5 . 'foo'
produces
error:imcc:object isn't a PMC
concatenation with . seems to be gone
i cannot think of a good replacement
On Mar-13, Luke Palmer wrote:
luka frelih writes:
But how should the two interpretations of x.x be resolved? Is that
concatenation or method calling?
currently, the pir line
S5 = S5 . 'foo'
produces
error:imcc:object isn't a PMC
concatenation with . seems to be gone
On Sat, 2004-03-13 at 17:07, luka frelih wrote:
But how should the two interpretations of x.x be resolved? Is that
concatenation or method calling?
wouldnt it be better to keep . as string glue
and have method calls use the arrow - or some
such?
Or follow perl6 and use ~ for string
The latest cvs of parrot fails to compile on mingw32,
In file included from include/parrot/parrot.h:258,
from src/utils.c:23:
include/parrot/misc.h:44: warning: `struct tm' declared inside parameter list
include/parrot/misc.h:44: warning: its scope is only this definition or
Hi,
On Saturday 13 March 2004 21:44, Dan Sugalski wrote:
At 9:06 PM +0100 3/13/04, Oli wrote:
Dan Sugalski wrote:
As well as involving much finding of instances, and moving of
their attribute
values, this isn't thread safe (please excuse my lack of PASM syntax
knowledge):
Yeah, adding an
On 2004-03-12, at 16:54:26 +, Arthur Bergman wrote:
This is Ponie, development release 2
First of all, this is just working great! All of my XS modules
compiled (almost) out of the box and worked really fine.
I noticed one small thing, however. The
At 02:42 PM 3/13/2004 -0800, Steve Fink wrote:
currently, the pir line
S5 = S5 . 'foo'
produces
error:imcc:object isn't a PMC
concatenation with . seems to be gone
i cannot think of a good replacement for it
This should be fixable with some lexer or parser tweaking.
Well,
25 matches
Mail list logo
