On Thu, 06 Mar 2003 05:51, Austin Hastings wrote:
> You'd like to declare the relationship between them, but this can be
> really difficult (consider e.g., nethack, in which the things you can
> "own" are constrained by weight/volume/knapsack).
> So certainly you need to be able to add code to the
On Fri, 07 Mar 2003 05:48, Garrett Goebel wrote:
> Over on perl6-internals you've been talking about the need for
> Associations. Is the addition of associations all that's missing from
> Parrot to support "exporting object relationships in a sensible and
> consistent manner"?
A prudent question.
On Thu, Mar 06, 2003 at 10:16:40AM +, Simon Cozens wrote:
: > Like mixins? Perhaps something like this:
: >
: > class My::Class;
: > mixin My::Random::Number::Generator qw( rand );
: > mixin My::Serialisation::Marshall qw( freeze thaw );
:
: Yey! With this, the Perl6-o-meter now stands
Leopold Toetsch wrote:
Joseph F. Ryan wrote:
I'm really curious as to this myself. I didn't even know an
"include" existed; its not in the imcc docs.
Its in docs/macros.pod, though this file is not mentioned in the main
doca AFAIK.
I don't have a docs/macros.pod. I guess my version of
At 10:48 AM -0600 3/6/03, Garrett Goebel wrote:
Sam Vilain wrote:
On Thu, 06 Mar 2003 05:10, Garrett Goebel wrote:
> Several people have mentioned a desire to see Perl6
> and Parrot facilitate object persistence. Should
> such issues be tackled in Parrot?
Not necessarily. Just be friendly to
Sam Vilain wrote:
Associations *are* fundamental object things. Presenting them in terms of
attributes is the real hack.
I agree with this statement; and Brent previously asked what
associations *are*. The problem with describing them in terms of
attributes/properties not not so much that its a
Sam Vilain wrote:
>
> On Thu, 06 Mar 2003 05:10, Garrett Goebel wrote:
> > Several people have mentioned a desire to see Perl6
> > and Parrot facilitate object persistence. Should
> > such issues be tackled in Parrot?
>
> Not necessarily. Just be friendly to object persistence
> frameworks by e
Hi,
I was just wondering about the tail call confusion around here.
Why not just mark a tail call in bytecode ?.
This is not strictly a new idea , and is "inspired" by:
"""
In addition, each of these instructions may be immediately preceded by a tail.
instruction prefix. This
On Thu, 06 Mar 2003 06:01, Dan Sugalski wrote:
> *) We're not talking perl 5 style objects, rather objects as
> fundamental things with attributes. Associations, from what I can see
> from your description, don't really apply.
I was talking about objects as fundamentals, too. I was just using Per
Joseph F. Ryan wrote:
I'm really curious as to this myself. I didn't even know an
"include" existed; its not in the imcc docs.
Its in docs/macros.pod, though this file is not mentioned in the main
doca AFAIK.
... I only bring this up
because around a month ago, I started working on use/inc
[EMAIL PROTECTED] (Andy Wardley) writes:
> Like mixins? Perhaps something like this:
>
> class My::Class;
> mixin My::Random::Number::Generator qw( rand );
> mixin My::Serialisation::Marshall qw( freeze thaw );
Yey! With this, the Perl6-o-meter now stands at:
PERL 5
K Stol wrote:
Hello,
Just 1 more question, for me to get it right.
When I have 2 modules, for example like this:
---main.imc---
.sub _main
bsr _hellosub
end
.end
.include hello.imc
--
---hello.imc--
.sub _hellosub
/* print "hello" or whatever */
ret
.end
---
K Stol wrote:
Hello,
Just 1 more question, for me to get it right.
When I have 2 modules, for example like this:
---main.imc---
.sub _main
bsr _hellosub
end
.end
.include hello.imc
--
---hello.imc--
.sub _hellosub
/* print "hello" or whatever */
ret
.end
---
Allison Randal (via RT) wrote:
# New Ticket Created by Allison Randal
# Please include the string: [perl #21476]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=21476 >
I couldn't compile imcc under OS X because of a repeat
Hello,
Just 1 more question, for me to get it right.
When I have 2 modules, for example like this:
---main.imc---
.sub _main
bsr _hellosub
end
.end
.include hello.imc
--
---hello.imc--
.sub _hellosub
/* print "hello" or whatever */
ret
.end
-
Sam Vilain wrote:
> No. All I'm saying is that this sort of construct:
>
>*{$_} = \&{"Class::$_"} foreach (qw(method method2 method3));
Like mixins? Perhaps something like this:
class My::Class;
mixin My::Random::Number::Generator qw( rand );
mixin My::Serialisation::Marshall qw( fre
16 matches
Mail list logo
