I have checked in various changes, cleanups, enhancements:
- classes/default.pmc: 2 step hash creation for properties
- classes/pmc2c.pl: --tree options prints classes hierarchy, missing
constand_FLAG for classnames
- list.h/list.c: move flags out of buffer header
- remove uninitialized warning fo
Dan Sugalski wrote:
At 4:17 PM + 1/9/03, Nicholas Clark wrote:
On Thu, Jan 09, 2003 at 01:32:57PM +0100, Leopold Toetsch wrote:
But I still favor the combination of:
- code reordering, like done for pmc_new
- DOD/GC disabling (e.g. aggregate clone)
- active anchoring to the root set,
On Thu, Jan 09, 2003 at 04:29:19PM +, Matthew Zimmerman wrote:
> # New Ticket Created by Matthew Zimmerman
> # Please include the string: [perl #19870]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19870 >
>
>
> A
On Thu, 9 Jan 2003 16:40:20 -0500, Dan Sugalski wrote:
> #10 We do MI, but we don't instantiate a class' attributes multiple
> times if its in the hierarchy for a class more than once. If it is, the
> leftmost instance is real, the rest are virtual
This will mean we can't support Eiffel, which
$ ./getparrot
can't create temporary directory /tmp/cvs-serv3864
No space left on device
On Jan-10, Leopold Toetsch wrote:
> Also I was thinking of: trace_system_areas could be run last in marking
> and if it finds some unanchored objects, it could print a warning, so we
> could really check, if we ware safe.
That's what defining GC_VERBOSE in parrot.h will give you right now,
and i
On Thu, Jan 09, 2003 at 07:55:20PM -0500, John Siracusa wrote:
> Has there been any discussion of how to create code in Perl 6 that's there
> under some conditions, but not there under others? I'm thinking of the
> spiritual equivalent of #ifdef, only Perlish.
>
> In Perl 5, there were many attem
On Thu, Jan 09, 2003 at 11:15:49PM -0500, John Siracusa wrote:
> On 1/9/03 10:10 PM, Michael G Schwern wrote:
> > I would assume it to be a compiler hint via subroutine attribute.
> >
> > sub debug ($msg) is off {
> > print STDERR $msg;
> > }
> >
> > some "this subroutine is a no-op if a
> print sort { ... } <~ mymethod(42) <~ @b;
>
> call sort on what comezouta calling mymethod(42) on what comezouta @b.
> I think. Indirect objects are still somewhat confusing. :)
>
> If I'm reading the info right on <~, then we want to make it clear
> that you _don't_ put it between print and stu
On 1/9/03 11:27 PM, Michael G Schwern wrote:
> On Thu, Jan 09, 2003 at 11:15:49PM -0500, John Siracusa wrote:
>> On 1/9/03 10:10 PM, Michael G Schwern wrote:
>>> I would assume it to be a compiler hint via subroutine attribute.
>>>
>>> sub debug ($msg) is off {
>>> print STDERR $msg;
>>> }
John Siracusa <[EMAIL PROTECTED]> wrote:
>
> Well, er, don't we need to decide what the subroutine attribute is, so that
> the compiler will know to honor it and make the code "disappear"? It
> doesn't seem like a feature that can be added from "userland" after the fact
> (but maybe I'm wrong...)
attriel wrote:
AssignmentOK?Because...
========
my Basket $c = $a no $c's type: Basket (of Object)
X ^
Andy Wardley wrote:
s/~=/=~/
Indeed. And that's precisely why we're changing it to ~~ in Perl 6. ;-)
The first 3 all relate to the familiar concept of 'minus', or more
precisely a delta between two values. The last uses '-' as 'dash',
another familiar concept which doesn't grate against th
Mr. Nobody wrote:
I find the normal function call and assignment far more readable than using
some weird ugly operator.
and later:
That's going to be just plain confusing. Arguments to functions are supposed
to be on the right. And what's up with using them for assignment? That's
making them
Damian Conway <[EMAIL PROTECTED]> writes:
> attriel wrote:
>
>> AssignmentOK?Because...
>> ========
>> my Basket $c = $a no $c's type: Basket (of Object)
>>
On Jan-09, Leopold Toetsch wrote:
> I have here now ~15 files different to CVS, which I would like to sync
> in either direction for easier future changes.
> So the question is, should I checked it in / partially / forget it.
>
> Changes are:
> - SPMC (small or scalar PMC) with half the size of a
Leopold Toetsch wrote:
> $ ./getparrot
> can't create temporary directory /tmp/cvs-serv3864
> No space left on device
Oops.
Fixed.
-R
> On Thu, 9 Jan 2003 16:40:20 -0500, Dan Sugalski wrote:
>> #10 We do MI, but we don't instantiate a class' attributes multiple
>> times if its in the hierarchy for a class more than once. If it is,
>> the leftmost instance is real, the rest are virtual
My only question here is: What is leftmos
At 1:37 PM + 1/10/03, Peter Haworth wrote:
On Thu, 9 Jan 2003 16:40:20 -0500, Dan Sugalski wrote:
#10 We do MI, but we don't instantiate a class' attributes multiple
times if its in the hierarchy for a class more than once. If it is, the
leftmost instance is real, the rest are virtual
At 10:37 AM -0500 1/10/03, attriel wrote:
> On Thu, 9 Jan 2003 16:40:20 -0500, Dan Sugalski wrote:
#10 We do MI, but we don't instantiate a class' attributes multiple
times if its in the hierarchy for a class more than once. If it is,
the leftmost instance is real, the rest are virtual
My
I did check in the clone changes.
- the clone vtable method get's now a dest ptr of an already created PMC
- so the newly created PMC is already anchored, which makes it possible
to change clone() code, so that no unanchored objects hang around, which
still is a TODO for more complex objects
- do
Steve Fink wrote:
On Jan-09, Leopold Toetsch wrote:
So the question is, should I checked it in / partially / forget it.
Changes are:
- SPMC (small or scalar PMC) with half the size of a PMC, no promotion
or whatever to a PMC, disabled with one define in pmc.c
- pool flags with aligned pools,
Steve Fink wrote:
On Jan-10, Leopold Toetsch wrote:
Also I was thinking of: trace_system_areas could be run last in marking
and if it finds some unanchored objects, it could print a warning, so we
could really check, if we ware safe.
That's what defining GC_VERBOSE in parrot.h will give you
Dan Sugalski wrote:
> and who's got
> questions on how this works? (I can put together examples, but this
> is pretty long as it is, and I think it's reasonably
> self-explanatory. Besides, assembly language isn't generally the best
> way to demonstrate anything... :)
Well, as far as I'm concerned
--- attriel <[EMAIL PROTECTED]> wrote:
> Could someone explain how to know what's the indirect object? (who
> knew
> the "sentence diagramming" would be USEFUL!!)
Short version:
If there's two people in the sentence, the verb-ee is either the direct
or indirect object. If there's two people and
On Thu, 09 Jan 2003 19:55:20 -0500
John Siracusa <[EMAIL PROTECTED]> wrote:
> Has there been any discussion of how to create code in Perl 6 that's
> there under some conditions, but not there under others? I'm thinking
> of the spiritual equivalent of #ifdef, only Perlish.
If the perl6 command-l
Damian Conway said:
> Andy Wardley wrote:
>> The arrow is a special case. I don't read that first character
>> as '-', I think of the operator as one. I guess the visual cue forces
>> me to see it like that.
>
> I'm suggesting that ~> and <~ will be the same.
I think that in part this may depe
On 1/10/03 11:11 AM, Dan Brook wrote:
> On Thu, 09 Jan 2003 19:55:20 -0500
> John Siracusa <[EMAIL PROTECTED]> wrote:
>> Has there been any discussion of how to create code in Perl 6 that's
>> there under some conditions, but not there under others? I'm thinking
>> of the spiritual equivalent of #
John Siracusa asked:
Has there been any discussion of how to create code in Perl 6 that's there
under some conditions, but not there under others? I'm thinking of the
spiritual equivalent of #ifdef, only Perlish.
In Perl 5, there were many attempts to use such a feature for debugging and
assert
Trey Harris raised the spectre of:
shades of C++, how about just
$*STDERR <~ $foo;
Yes. Assuming C were suitably overloaded.
or
$foo ~> $*STDERR;
Yes. Assuming C were suitably overloaded.
Not sure whether that would come "standard", but if not, here's
a first cut of the necessary mod
Damian Conway wrote:
Can I suggest that an alternative solution might be the following:
So an L2R array-processing chain is:
@out = @a ~> grep {...} ~> map {...} ~> sort;
There might also be a be special rule that, if the RHS is
a variable, the LHS is simply assigned to it.
On 1/10/03 12:24 PM, Damian Conway wrote:
> "Immediate" subroutines are executed as soon as they are parsed (i.e. they're
> like named BEGIN blocks).
>
> Returning a closure/block from an immediate sub called in a void context
> (as C is in the example above) causes the immediate sub call to be
>
On Thursday, January 9, 2003, at 03:24 AM, Damian Conway wrote:
Michael Lazzaro asked:
class FileBasedHash is Hash { ...stuff... };
my %data is FileBasedHash('/tmp/foo.txt');
Yes.
my $path = '/tmp/foo.txt';
my %data is FileBasedHash($path);
Indeed
Great -- then I have only one
--- attriel <[EMAIL PROTECTED]> wrote:
> Ah. OK, thanks :) I had the basic idea, but I wasn't sure how to
> tell in perl which parameter was the indirect object :o
Right, "o" in your sentence above is the object.
> if I'm following this right, it's the inferred object such that (in
> p5) if I
On Fri, Jan 10, 2003 at 10:28:49AM -0800, Michael Lazzaro wrote:
> Great -- then I have only one more question, I think. In the words of
> a certain cartoon character, what's *this* button do?
>
>my $b is $a;
And no matter what that button does, will this:
my $a $b;
be illegal?
-
On Friday, January 10, 2003, at 11:49 AM, Dan Sugalski wrote:
At 1:37 PM + 1/10/03, Peter Haworth wrote:
This will mean we can't support Eiffel
Nope. :)
What it means is that the proposed base object system won't work for
eiffel.
Actually, if you really want Eiffel to compile to Parrot,
> -Original Message-
> From: Leopold Toetsch [mailto:[EMAIL PROTECTED]]
>
> Further remark: the scratchpad clone code looks dubious, the 2 lists in
> the data (lex) entry should probably cloned too - and at least the lex
> ptrs themselves.
> The destroy method leaks, because we can't cleanu
Here are some examples from Object Oriented Software Construction (Second
Edtion), Chapter 15 (Multiple Inheritance):
* Simple multiple inheritance:
class PLANE ...
class ASSET ...
class COMPANY_PLANE inherit PLANE ASSET ...
or
class TREE [G] ... -- Param
On Friday 10 January 2003 11:42 am, Paul Johnson wrote:
> Damian Conway said:
> > Andy Wardley wrote:
> >> The arrow is a special case. I don't read that first character
> >> as '-', I think of the operator as one. I guess the visual cue forces
> >> me to see it like that.
> >
> > I'm suggesting
From: Michael Lazzaro [mailto:[EMAIL PROTECTED]]
> But I don't know if these two
> lines would really have the same result, ...
>
> $a = MyScalar;
> $a = 'MyScalar';
Hrmm. Didn't Larry decree that there are no bare words, but that a class
name will evaluate to the string representing th
Paul Johnson <[EMAIL PROTECTED]> wrote:
> When I later saw it using mutt in an xterm, the tilde was at the top of
> the character, where I was more used to seeing it and it didn't look like
> an arrow any more, nor did it look very good to me.
Well, at least now I understand why some people didn't
Andrew Rodland <[EMAIL PROTECTED]> wrote:
> But you're missing the most important part!
> I propose that these operators should be named "gozinta" ( ~>)
> and "comezouta" ( <~ ), just so that we can say that perl has them. Not to
> mention that the names work pretty well, for me.
Here, here! Al
> Date: Fri, 10 Jan 2003 08:12:48 -0800 (PST)
> From: Austin Hastings <[EMAIL PROTECTED]>
>
> --- attriel <[EMAIL PROTECTED]> wrote:
> > Could someone explain how to know what's the indirect object? (who
> > knew
> > the "sentence diagramming" would be USEFUL!!)
>
> Short version:
>
> If there'
> From: Thom Boyer <[EMAIL PROTECTED]>
> Date: Fri, 10 Jan 2003 13:57:26 -0700
>
> From: Michael Lazzaro [mailto:[EMAIL PROTECTED]]
> > But I don't know if these two
> > lines would really have the same result, ...
> >
> > $a = MyScalar;
> > $a = 'MyScalar';
>
> Hrmm. Didn't Larry decr
Paul Johnson wrote:
> When I later saw it using mutt in an xterm, the tilde was at the top of
> the character, where I was more used to seeing it and it didn't look like
> an arrow any more, nor did it look very good to me.
Ah yes, that's the problem. On all my fonts, the tilde appears at
the top
On Fri, Jan 10, 2003 at 03:55:30PM -0500, Andrew Rodland wrote:
> On Friday 10 January 2003 11:42 am, Paul Johnson wrote:
> > Damian Conway said:
> > > Andy Wardley wrote:
> > >> The arrow is a special case. I don't read that first character
> > >> as '-', I think of the operator as one. I guess
Let me just chime in here that I have been reading all the
messages via mutt in an xterm font in which the
tilde is at the top of the space, and this has in no way
affected my appreciation of the new operators.
I don't want them to look like arrows, because that's reminiscent
of ->, which is misle
The attached patch fixes the problem. It changes Scratchpad's data pointer
to be a pointer to an array of Parrot_Lexicals (rather than an array of
pointers to Parrot_Lexicals). The (name and value) lists are shared but
never the actual Parrot_Lexical ptr. So no more leak.
Patch touches:
-- class
On Jan-10, Leopold Toetsch wrote:
>
> You get double the amount of PMCs into the cache - used during marking
> and freeing. It isn't related to alignment, just more throughput.
Oh. You're right. I was thinking that the unused portion of the PMC
wouldn't need to be loaded into the cache, so that
If memory serves me right, Chris Dutton wrote:
> Actually, if you really want Eiffel to compile to Parrot, it might be
> interesting to work on getting ANSI C to compile to Parrot first, since
> most Eiffel compilers use compilation to C as an intermediate step.
This won't be too much of stretch
I don't know about *your* font, but in mine the ~> and <~ versions are
at least twice as readable as the |> and <| ones.
Just out of curiosity, how did you measure that? ;-)
Well, obviously, I used the Symbol::Readability module:
module Symbol::Readability;
sub delta_r(Str $a, Str $a) retur
51 matches
Mail list logo
