On Thu, 26 Sep 2002, Joe Gottman wrote:
: Apocalypse 4 mentions unary '?' . Since this is used to force boolean
: context, I would assume that it has the same precedence as unary '+' and
: '_' which force numeric and string context respectively. By the way, has
: anyone come up with a use
There were a number of warnings which read something like
"structure padded for alignment of member value in debug.h"
This can be trivially fixed by reordering the structure members ( I hope).
This patch works fine on cygwin, but I would like to see some other
platforms (especially 64 bit) try it
>2.) You mention getting a Perl distribution for Windows, but don't metnion
>getting a C compiler.
> I would recommend saying something about CygWin (www.cygwin.com) or
>perhaps a dos based C compiler. cvs, perl, and make all become non-issues
>when CygWin is added to the mix; although perfo
>Well here it is, my first attempt at a "getting started" guide. It's
>not ready for public consumption, but I would like to hear some
When this stabilizes, we can make it available on www.parrotcode.org
>I plan to have a lot more diagrams in the document. I am using 'dia'
>to create them. I
Great document. I have a couple of comments.
1.) The beginning talks a lot about people doing this "on the job". A lot
of developers on open source projects are students, you might wish to
mention something just to acknowledge that they do exist. I know it is
petty, but it never hurts to feed
On Sat, Sep 21, 2002 at 11:41:38AM +, Leopold Toetsch wrote:
>
> This patch
> - removes check_fingerprint (this should be done in PBC unpack)
> - simplifies init_prederef
> - separates dynamic oplib loading from prederef
> - changes not to run prederef, when e.g. tracing is on
> - avoids an e
A *very* nice start. Please don't burn yourself out, though -- I got
worried when you gave the whole rundown on the configure system. It's
a great thing to have documented, but it's a lot to wade through
before getting into the juicy bits. (For you, I mean -- it's
sufficiently brief in the documen
Hi,
Well here it is, my first attempt at a "getting started" guide. It's
not ready for public consumption, but I would like to hear some
feedback. The later sections are blank or contain notes in a not nice
format. As time moves on and I learn more, I expect the guide to fill
up. It's ta
On Tue, Oct 01, 2002 at 07:23:24AM +, Leopold Toetsch wrote:
> # New Ticket Created by Leopold Toetsch
> # Please include the string: [perl #17702]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=17702 >
>
>
> This
On Tue, Oct 01, 2002 at 07:23:28AM +, Leopold Toetsch wrote:
> # New Ticket Created by Leopold Toetsch
> # Please include the string: [perl #17705]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=17705 >
>
>
> This
On Tue, Oct 01, 2002 at 07:23:27AM +, Leopold Toetsch wrote:
> # New Ticket Created by Leopold Toetsch
> # Please include the string: [perl #17704]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=17704 >
>
>
> This
Thanks, applied.
Thanks, applied.
Who came up with the idea of two-argument ne, anyway? That's kind of
bizarre. I'd much rather have it tested if it exists at all, but it
seems pretty obscure.
According to Larry Wall:
> On Sat, 5 Oct 2002, Chip Salzenberg wrote:
> : I rather like Perl 5's scalar comma operator.
>
> Most of the uses of which are actually in void context [...]
I didn't realize you were distinguishing scalar from void in this, uh,
context. I agree that scalar comma is e
On Tue, 8 Oct 2002, Larry Wall wrote:
: : perl6 operator precedence
: :
: :leftterms and list operators (leftward) [] {} () quotes
: :left. and unary .
:
: Unary . can't be left associative. Perhaps unary . is nonassoc like ++.
Actually, unary . has to b
On Thu, 26 Sep 2002, John Williams wrote:
: I'm trying to write a revised operator precedence table for perl6,
: similar to the one in perlop.pod.
:
: This is what I have come up with based on Apocalypse 3 and Exegesis 3.
: Does anyone have comments? I'm not sure if the precedence
: for : (ad
On Thu, 26 Sep 2002, Sean O'Rourke wrote:
: Thanks for taking the time to write this out.
:
: On Thu, 26 Sep 2002, John Williams wrote:
: > perl6 operator precedence
: >
: >leftterms and list operators (leftward) [] {} () quotes
: >left. and unary .
: >
On Fri, 27 Sep 2002, Dan Sugalski wrote:
: At 12:40 PM -0700 9/26/02, Sean O'Rourke wrote:
: >On Thu, 26 Sep 2002, Paul Johnson wrote:
: >> Is that sufficiently vague?
: >
: >Not vague enough, because the current implementation manages to miss the
: >broad side of that semantic barn...
:
: The i
On Sat, 5 Oct 2002, Chip Salzenberg wrote:
: According to Larry Wall:
: > I suppose we could make comma merely puke in scalar context rather
: > than DWIM, at least optionally.
:
: I rather like Perl 5's scalar comma operator.
Most of the uses of which are actually in void context, where it
does
On Sun, 6 Oct 2002, Trey Harris wrote:
: In a message dated Sun, 6 Oct 2002, Noah White writes:
: > On Sunday, October 6, 2002, at 01:50 AM, Brent Dax wrote:
: >
: > > Parens don't construct lists EVER! They only group elements
: > > syntactically. One common use of parens is to surround a
: >
On 6 Oct 2002, Smylers wrote:
: Do parens still provide list context on the left side of an assignment?
Er, kind of. More precisely, use of parens on the left provides a
flattening list context on the right side, just as in Perl 5. I guess
I did not make clear that a basic Perl 6 design decisio
# New Ticket Created by Jonathan Sillito
# Please include the string: [perl #17811]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17811 >
I have been playing with classes and instances for parrot. In
the process I found
Take a look at:
http://java.sun.com/products/jdk/1.2/docs/guide/collections/designfaq.html
Either you agree with the answer to "Core Interfaces" questions 1 and 2 or
you don't. There are tradeoffs to be made, and I think they made some
reasonable choices, though others are free to think otherwis
On Tue, Oct 08, 2002 at 04:32:40PM -0400, Trey Harris wrote:
> In a message dated Tue, 8 Oct 2002, Allison Randal writes:
> > Hmmm... I can see how it might be handy if C would just
> > grab the highest numbered "Acme::N..." module on the system.
>
> After a
>
> no strict 'versions';
>
> please
On Tue, Oct 08, 2002 at 05:03:26PM -0400, Trey Harris wrote:
> > It really ought to be one of those "sure you can do this, but please don't"
> > things.
>
> It's a RuntimeException. You can't require that all RuntimeExceptions be
> declared if thrown;
> You can subclass RuntimeException. So if
Steve Fink wrote:
> On Mon, Oct 07, 2002 at 11:25:31PM +0200, Leopold Toetsch wrote:
>>If conserving memory is an issue, list.c is much more efficient for very
>>small and very big arrays. We will see.
>>
>
> Sounds good to me. I originally wrote, and am currently using, intlist
> for regular
In a message dated Tue, 8 Oct 2002, Michael G Schwern writes:
> On Sun, Oct 06, 2002 at 06:17:37PM -0400, Daniel B. Boorstein wrote:
> > I think there may be some confusion here. In java, there's no special syntax
> > to declare a method an optional part of the interface. All concrete classes
> >
On Sun, Oct 06, 2002 at 11:57:51PM -0400, Noah White wrote:
> I wouldn't call it a dirty little secret as Michael put it :-).
> This is the right thing to do within the context of a contract. The
> contract does not guarantee that method functionality implemented by a
> concrete cl
On Sun, Oct 06, 2002 at 06:17:37PM -0400, Daniel B. Boorstein wrote:
> I think there may be some confusion here. In java, there's no special syntax
> to declare a method an optional part of the interface. All concrete classes
> that implement the Collection interface still must define full-bodie
In a message dated Tue, 8 Oct 2002, Allison Randal writes:
> Hmmm... I can see how it might be handy if C would just
> grab the highest numbered "Acme::N..." module on the system.
After a
no strict 'versions';
please. :-)
Trey
On Mon, Oct 07, 2002 at 05:56:19PM -0700, chromatic wrote:
> On Sat, 05 Oct 2002 15:51:04 -0700, Allison Randal wrote:
>
> >
> > class A would have:
> >
> > use Acme::N-1_0; # or whatever the format of the name is
> >
> > while the updated class B would have:
> >
> >use Acme::N-1_1;
>
# New Ticket Created by Simon Glover
# Please include the string: [perl #17803]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17803 >
The patches below add tests for:
print_i_i
print_i_n
print_i_s
print_i_p
n
# New Ticket Created by Simon Glover
# Please include the string: [perl #17802]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17802 >
Should be self-explanatory.
Simon
--- core.ops.oldTue Oct 8 14:09:08 2
Andy Dougherty:
# After just this little patch: (line numbers are off due to
# other unrelated fiddling on my part)
#
# it compiles. So far, I only have seen 2 failed tests:
#
# The first is t/src/sprintf.t, which looks like an off-by-one
# issue of some sort. I haven't tracked it further y
On Tue, 8 Oct 2002, Brent Dax wrote:
> OK. This is a pretty big patch. (Fine--*really* big, at 117K. :^) )
>
> First of all, it completes the feature set of the Parrot_sprintf family,
Thanks!
After just this little patch: (line numbers are off due to other
unrelated fiddling on my part)
--
On Mon, Oct 07, 2002 at 11:25:31PM +0200, Leopold Toetsch wrote:
> So, if people are ok with this, i'll commit it as list.c in parrot's
> root (+ some more t/pmc/intlist.t). Transition of array.pmc may then
> follow later.
>
> It's currently not intended to replace intlist.c, I don't know the
Leon Brocard wrote:
> Leopold Toetsch sent the following bits through the ether:
>
>
>>So I rewrote the base routines almost from scratch and have currently a
>>file named list.c
>>
>
> I for one am confused as to the number of array-like classes in
> Parrot. What is the differe
I discovered the problem:
print "Yes r\n" if "0" =~ /0/;
print "Yes s\n" if "0" =~ "0";
printed only "Yes s"
The problem is NOT in the RE engine, but in the string literal code in
P6C/Tree/String.pm
I replaced some "if ($stuff)" with "if (defined $stuff)" and now it
works. The problem was
Leopold Toetsch sent the following bits through the ether:
> So I rewrote the base routines almost from scratch and have currently a
> file named list.c
I for one am confused as to the number of array-like classes in
Parrot. What is the difference between list and array? Or intlist? Or
multiarr
On Wed, 02 Oct 2002 04:12:44 -0700, Michael G Schwern wrote:
> I like the "class Vehicle is interface" as a shorthand for declaring every
> method of a class to be an interface.
Perhaps associating a property with a class can be shorthand for associating
that property with every method of the cl
On Sat, 05 Oct 2002 15:51:04 -0700, Allison Randal wrote:
> On Sat, Oct 05, 2002 at 02:50:11PM -0400, Trey Harris wrote:
>> Ah, but the usual case is this:
>> You download from CPAN class A that depends on version 1.0 of class N. You
>> then download class B that also depends on version 1.0 of
41 matches
Mail list logo
