--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> James Michael DuPont (via RT) wrote:
>
> >>--- packdump.c 2 Nov 2002 14:57:47 - 1.6
> >>+++ packdump.c 4 Jan 2003 16:18:37 -
>
>
> >>+#ifdef HAS_parrot_string_t_flags
>
> This is already fixed.
thanks, I have not
On Thursday 09 January 2003 01:01 pm, Thom Boyer wrote:
> If you read ~> and <~ as "stuff this thingy into that doohicky", assignment
> makes perfect sense. They are plumbing connectors: sometimes they connect
> the water softener to the water heater (one device to another), and
> sometimes they co
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 flag is set" attribute.
Hm, not quite as convenient as setting a package globa
On 1/9/03 9:01 PM, Luke Palmer wrote:
> Well, I just do:
>
> sub debug {
> print STDERR shift, "\n" if DEBUG;
> }
>
> And hopefully (I don't know P5 internals so well) that optimizes to a
> no-op so there's not even a function call there.
I don't know P5 internals so well either, but I'm guess
> Date: Thu, 09 Jan 2003 19:55:20 -0500
> From: John Siracusa <[EMAIL PROTECTED]>
>
> 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,
On Thursday, January 9, 2003, at 03:05 AM, Damian Conway wrote:
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? ;-)
David
--
David Wheeler
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
assertions. What everyone wa
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, where above is not appli
At 5:46 PM +0100 1/9/03, Leopold Toetsch wrote:
Nicholas Clark wrote:
ie user code has to have the discipline either to have things linked to the
root set by the time it makes a parrot call or explicitly disable DOD across
such a call.
Yes. We need some XS guidelines anyway. One more rule or l
At 1:46 PM +0100 1/9/03, Leopold Toetsch wrote:
Leopold Toetsch wrote:
Steve Fink wrote:
(3) propose something else that solves the whole problem neatly.
i.e. reorder code where possible, and anchor early,
RFC: changing the clone op functionality slightly:
Clone does in the first step p
Okay, as promised, here's the object proposal for parrot. (And yes,
it was finished by 5PM EST--if you got it later, it just means I
lingered over coffee in a blissfully wireless-free coffee shop down
the street from my apartment)
Objects, as far as I see it, have the following properties:
1) The
At 2:31 AM -0500 1/9/03, Joseph F. Ryan wrote:
Dan Sugalski wrote:
Could one of the folks working on the perl 6 parser give us a
status update as to where it stands? Which bits of the apocalypses
don't work, and what parts of the regex definiton's not done yet?
Things have stalled a bit, and
At 3:46 PM -0800 1/8/03, Zach Lipton wrote:
I am pleased to announce that LXR has been installed on perl.org to index
the source of parrot and perl5 (additional modules, such as perl6, can be
added as needed).
Cool. Thanks, Zach.
--
Dan
--
James Michael DuPont (via RT) wrote:
--- packdump.c 2 Nov 2002 14:57:47 - 1.6
+++ packdump.c 4 Jan 2003 16:18:37 -
+#ifdef HAS_parrot_string_t_flags
This is already fixed.
leo
Dan Sugalski wrote:
... (And I don't want
to go with an extra level of indirection for this, for speed reasons)
I did answer, nor do I, but recent cache coherency discussion could
imply, that eg. this wouldn't be to bad.
I thought of:
- a PMC is a handle (index) into
- array of pointers (e.g
On Wed, Jan 08, 2003 at 05:59:14PM +0800, Damian Conway wrote:
> > my Array @array := SpecialArray.new;
> >
> > Should the value in @array act like an Array or a SpecialArray? Most
> > people would say SpecialArray, because a SpecialArray ISA Array.
>
> Weell...*I'd* say that @array shoul
Mr. Nobody:
# It's not letting you do anything that you couldn't do before
# with normal function calls and assignment.
We're writing a useful language, not a Turing machine.
# I see it as making a bad idea even worse. I've never liked
# having one thing doing multiple completely different and
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> --- Thom Boyer <[EMAIL PROTECTED]> wrote:
> > Mr. Nobody <[EMAIL PROTECTED]> wrote:
> > > --- Damian Conway <[EMAIL PROTECTED]> wrote:
> > > > @a ~> grep {...} ~> map {...} ~> sort ~> @out;
> > >
> > > That's going to be just plain confusing.
--- Thom Boyer <[EMAIL PROTECTED]> wrote:
> Mr. Nobody <[EMAIL PROTECTED]> wrote:
> > --- Damian Conway <[EMAIL PROTECTED]> wrote:
> > > @a ~> grep {...} ~> map {...} ~> sort ~> @out;
> >
> > That's going to be just plain confusing. Arguments to functions are
> supposed
> > to be on the ri
On Thu, Jan 09, 2003 at 11:01:51AM -0700, Thom Boyer wrote:
> Mr. Nobody <[EMAIL PROTECTED]> wrote:
> 3) "Do you care about readability at all? It seems to me that ~> and <~
> have no use except making perl 6 uglier and more complicated than it already
> is."
>
> I think ~> and <~ look pretty nic
Mr. Nobody <[EMAIL PROTECTED]> wrote:
>
> --- Damian Conway <[EMAIL PROTECTED]> wrote:
> > @a ~> grep {...} ~> map {...} ~> sort ~> @out;
>
> 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? Th
(/dks attempts to pour water.)
Damian Conway <[EMAIL PROTECTED]> wrote:
> > And even if we do have both functional and methodical versions, this:
> >
> > @out <~ sort <~ map {...} <~ grep {...} <~ @a;
> >
> > is still clearer in its intent than:
> >
> > @out = sort map {...} gre
At 2:08 PM + 1/9/03, Peter Haworth wrote:
On Wed, 8 Jan 2003 15:39:52 -0500, Dan Sugalski wrote:
At 7:29 PM -0700 1/7/03, John Williams wrote:
>Perhaps you could explain how the $0 object will work in your mind.
>A5 assert that $0 is a object, and it behaves as an array and a hash,
>depen
--- Damian Conway <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
>
> > I don't like either of these operators. What's wrong with
> >
> > @out = sort map {...} grep {...} @a
> >
> > ?
>
> For a start, if these functions were to become (only) methods in Perl 6,
> it would have to be:
>
>
Damian Conway writes:
> Unary ~> would (by analogy to unary dot) append the current topic to the
> argument list of its operand.
>
> Thus, your examples become simply:
>
> given @list {
> ~> grep /bad!/ ~> @throw;
> ~> grep /good/ ~> @keep;
>
# New Ticket Created by James Michael DuPont
# Please include the string: [perl #19874]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19874 >
this is the patch to compile pdump under linux
basically it removes a field that
Matthew Zimmerman (via RT) 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 CVS update from about 30 minutes ago is faili
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, where above is not applicable
Which combined mea
# New Ticket Created by James Michael DuPont
# Please include the string: [perl #19873]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19873 >
bug report for parrot/languages/perl6
mike
--- James Michael DuPont <[EMAIL PRO
# New Ticket Created by James Michael DuPont
# Please include the string: [perl #19872]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19872 >
Missing header file for cygwin
--- James Michael DuPont <[EMAIL PROTECTED]> wro
# New Ticket Created by James Michael DuPont
# Please include the string: [perl #19871]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19871 >
Attached is the bug report and test results for
parrot on cygwin.
--- James Mi
# 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 CVS update from about 30 minutes ago is failing to compile
on my Red Hat Linux 7.
>> I'm just suggesting the same for the ~ character:
>>
>> ~~ smart-match
>> ~concatenate
>> ~| stringy bitwise OR
>> ~> append args
>> <~ invocate
>
> This is where I get lost. I see 4 different concepts being overloaded
> onto '~'.
>
> In the first it indicates 'm
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, where above is not applicable
Which combined means that there is no
> my Set of Apple $a;
> my Basket of Fruit $b;
>
> and a generic assignment:
>
> $c = $a;
> $c = $b;
>
> Now we can fill in your list (which is somewhat expanded):
>
AssignmentOK?Because...
=======
On Thursday, January 9, 2003, at 05:36 AM, Damian Conway wrote:
Chris Dutton wrote:
@ages[*] = $today - %date_of_birth{@names}.values[*]
Well done. Thanks for working that out, Chris. And, in the process,
confirming my sense that vector ops are a better solution here.
;-)
Glad I could cont
On Thu, 9 Jan 2003, Peter Haworth wrote:
> On Wed, 8 Jan 2003 15:39:52 -0500, Dan Sugalski wrote:
> > At 7:29 PM -0700 1/7/03, John Williams wrote:
> > >Perhaps you could explain how the $0 object will work in your mind.
> > >A5 assert that $0 is a object, and it behaves as an array and a hash,
>
On Wed, 8 Jan 2003 15:39:52 -0500, Dan Sugalski wrote:
> At 7:29 PM -0700 1/7/03, John Williams wrote:
> >Perhaps you could explain how the $0 object will work in your mind.
> >A5 assert that $0 is a object, and it behaves as an array and a hash,
> >depending on how you subscript it. Typeglobs are
Mr. Nobody wrote:
I don't like either of these operators. What's wrong with
>
> @out = sort map {...} grep {...} @a
>
> ?
For a start, if these functions were to become (only) methods in Perl 6,
it would have to be:
@out = sort map grep @a: {...} : {...} :;
And even if we do have
Michael Lazzaro asked:
OK, next question. Is _THIS_ possible?
class FileBasedHash is Hash { ...stuff... };
my %data is FileBasedHash('/tmp/foo.txt');
Yes. Though we would need a syntax for specifying that string parameter for the
generic C class. And, of course, a mechanism for constru
Damian Conway wrote:
> Really? We don't have any trouble in Perl 5 with an = character
> being used in various unrelated operators:
>
> == comparison
> =assignment
> ~= match
s/~=/=~/
> => comma
> <= less than or equal to
But these are all roughly related to the
Piers Cawley wrote:
alloc_and_link( void ** handle, size_t size);
This is covered in Steve Finks summary as solution 3.
There were also two code snippets by Brent Dax and Jerome Vouillon, that
deal with exception handling too. s. thread "Infant mortality" started
by Steve.
Note that NU
Leopold Toetsch wrote:
Steve Fink wrote:
(3) propose something else that solves the whole problem neatly.
i.e. reorder code where possible, and anchor early,
RFC: changing the clone op functionality slightly:
Clone does in the first step pmc_new{,noinit} a PMC of the desired type.
This
In a message dated Thu, 9 Jan 2003, Damian Conway writes:
> One *might* argue that <~ ought to be of higher precedence than ~>
> (i.e. that invocants ought to be bound ahead of other arguments).
>
> If so, then:
>
>$foo ~> print <~ $*STDERR
>
> is really:
>
>$foo ~> print $*STDERR:
Andy Wardley wrote:
I also think this is semantically fabulous but syntactically slightly
dubious. '~' reads 'match' in my book,
Really? We don't have any trouble in Perl 5 with an = character
being used in various unrelated operators:
== comparison
=assignment
~= match
Chris Dutton wrote:
For example, I'm struggling to see how one could use the [*] to do this:
@names = «Gödel Escher Bach»;
@ages = $today »-« %date_of_birth{@names}
While I agree that hyper-operators are the better way to go(though I can
see advantages either way), I was bored, s
Rafael Garcia-Suarez asked:
> Damian Conway <[EMAIL PROTECTED]> wrote:
>
>>There are in fact *two* types associated with any Perl variable
>
> How does it work regarding inheritance and polymorphism ?
> E.g. consider
> my @a is Set of Apple;
> my @b is Basket of Fruit;
> with Apple isa Fruit,
frederic fabbro wrote:
I'm not even sure how that would parse, though that:
>
@keep <~ grep /good/ <~ @list ~> grep /bad!/ ~> @throw;
>
would go like:
>
( @keep <~ grep /good/ <~ @list ) ~> grep /bad!/ ~> @throw;
Correct, if <~ is indeed slightly higher precedence than ~>
which is pro
Jonathan Scott Duff suggested:
> Oh, then we just need a syntax to split the streams. ... I know!
>
> @list ~| grep /bad!/ ~> @throw ~| grep /good/ ~> @keep;
Unfortunately, that's already taken (it's the bitwise-OR-on-a-string operator).
Fortunately that doesn't matter, since no extra bina
Philip Hellyer wrote:
Damian's proposal didn't say anything about array params. If I understood
him correctly, then this should print "FOO" on standard out:
my $foo = "FOO";
$foo ~> print;
Correct.
The opposite 'squiggly arrow' fiddles the indirect object, so perhaps this
would pri
Sean O'Rourke wrote:
... The
tests should all still pass (barring inclement GC bugs), but they reflect
the outdated spec.
Almost:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/compiler/1.test
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 PMC, no promotion
or whatever to a PMC, disa
[EMAIL PROTECTED] (Mr. Nobody) writes:
> We can't use « or ». Not only are they impossible to type on some editors,
> but they're different in CP437 (the DOS charset), Latin1, and UTF8.
We've done this.
--
I've looked at the listing, and it's right!
-- Joel Halpern
This will be vague and handwavy, but I *think* it suggests something
that hasn't been tried before...
1. The problem of infant mortality is that resource allocation can
trigger a DOD run could wipe out the very thing we were allocating
memory for.
2. This can be solved by extending the root
54 matches
Mail list logo
