Jonathan Worthington wrote:
All that said, there is an argument for having it as a vtable method
that I think stands, which is the same argument that suggests not having
any methods on the class PMC at all and making everything a vtable
method. The argument is that if a language wants to inheri
Leopold Toetsch wrote:
The former is also implementing the Hash iteration internals. E.g.
switch (PObj_get_FLAGS(key) & KEY_type_FLAGS) {
case KEY_hash_iterator_FLAGS:
...
return parrot_hash_get_idx(INTERP, hash, key);
Yeah, that part's pretty
On 4/3/07, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
There is a compromise - make them all vtable methods, write a BaseClass
PMC and inherit Class from it. BaseClass implements all of the vtable
variants of the method, and Class can then provide a sane interface. HLL
implementers who need
On Monday 02 April 2007 17:19, Steve Peters via RT wrote:
> > Here's some additional cleanups for making Parrot a bit more friendly
> > to a wider variety of C compilers.
Thanks, applied as r17952.
-- c
On Mon Apr 02 17:16:45 2007, stmpeters wrote:
> Here's some additional cleanups for making Parrot a bit more friendly
> to a wider variety of C compilers.
>
It is always good to actually include the attachment you are sending.
Steve
Index: src/encoding.c
===
# New Ticket Created by Steve Peters
# Please include the string: [perl #42279]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42279 >
Here's some additional cleanups for making Parrot a bit more friendly
to a wider variety
Alek Storm wrote:
I was expecting new() to be a vtable method, since that is the only
way we can guarantee that whatever PMC comes out of find_class
implements new(). We don't want code to crash because somebody stuck
a non-class PMC into Parrot as a class.
Huh? A vtable method doesn't promise
On 3/31/07, Allison Randal <[EMAIL PROTECTED]> wrote:
Alek Storm wrote:
>>
>> $P0 = get_hll_namespace
>> $P1 = $P0.find_class("HLLClass")
>> $P2 = $P1.new()
>
>
> Will new() be a vtable method or PCCMETHOD in a Class PMC? That's the
only
> way I can see this syntax not conflicting with normal me
Allison Randal wrote:
So, perhaps we need:
$P2.resolve($P1)
Implemented this (both the interface and the semantics); test for it
added too.
Just got the changes to alias to handle, then hopefully role conflict
resolution is in sync with the PDD again.
Thanks for the clarifications,
Jonath
Am Montag, 2. April 2007 08:24 schrieb Allison Randal:
> The significant differences between the two are that Iterator's
> shift_pmc throws an exception if the iteration key is -1 while
> shift_string doesn't bother to check (it probably should), and
> shift_string calls VTABLE_get_string_keyed on
Am Montag, 2. April 2007 07:37 schrieb Joshua Isom:
> I'm not sure how the imcc compiler handles the .Foo syntax internally,
> but there's a file, runtime/parrot/include/pmctypes.pasm that at least
> appears as though it's magically included into the beginning of every
> pir/pasm file.
Nope the pm
I'm closing this ticket because the causes of the failing test files
have been identified in ongoing work by other project members and the
tests are no longer failing (or, at least, consistently failing).
No one has spoken up in favor of retaining the 'no-body' option. tewk,
who is doing as much work as anyone in this area, has recommended
getting rid of it.
I will take the ticket. Perl Seminar NY's Phalanx Phoenix project is
recruiting additional hackers to work on this type of code. We'll
assi
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Apr 2 13:00:03 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with mo
chromatic wrote:
On Sunday 01 April 2007 07:15, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
needs a "make cle
Steve Peters wrote:
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
n
Eric Hanchrow wrote:
"Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> If you see this error
...
Ron> the file has Windows line endings
Dare I suggest that parrot not be so fussy about line endings?
I second that. ;) Actually, both things are supposed only as
workarounds until
17 matches
Mail list logo
