Nicholas Clark wrote:
> I think that the first syntax
>
> class Car::Q is Car renames(eject => ejector_seat)
> is CD_Player renames(drive => cd_drive);
>
> makes it more clear that I'd like to pick and choose which methods
> the composite object gets from which parent.
But now you'
On Sunday 06 October 2002 09:57 pm, Michael G Schwern wrote:
> On Sun, Oct 06, 2002 at 01:49:26AM -0400, Noah White wrote:
> > >OTOH, Java interfaces have a loophole which is considered a design
> > >mistake.
> > >An interface can declare some parts of the interface optional and then
> > >implemen
On Sunday, October 6, 2002, at 12:57 AM, Noah White wrote:
>>
>>> Note that an alternate definition of "private" is often used, as
>>> follows:
>>>
>>> A "private" attribute is an attribute whose scope is restricted
>>> such that
>>> it may be accessed only within the class in which it
# New Ticket Created by "Paul Du Bois"
# Please include the string: [perl #17775]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17775 >
Some of the tests in t/src fail to run in win32 because the tests don't
compile. Thi
Dan Sugalski <[EMAIL PROTECTED]> writes:
> At 9:37 PM -0400 9/29/02, Mike Lambert wrote:
> >intlist is not the only culprit. ./classes/key.c and ./key.c have a
> >similar problem.
>
> Then let's start a convention.
>
> Classes start with a CL_ prefix, encodings with an EN_ prefix, and
> charact
On Tue, 1 Oct 2002, Brent Dax wrote:
> Andy Dougherty:
> # > *elbows him in the side and points at
> # /Parrot_v?sn?printf(_[sc])?/ in
> # > misc.c*
> #
> # Interesting, yes, that's mostly what I had in mind, but I'm
> # unsure just how it's intended to be used.[*] That is, if I have
> #
> #
At 9:16 AM + 10/7/02, "Paul Du Bois" (via RT) wrote:
>Some of the tests in t/src fail to run in win32 because the tests don't
>compile. This doesn't fix them (different patch), but it adds better
>reporting to Test.pm. Now you see the compile error instead of the shell's
>" doesn't exist" er
Hi!
I just found a strange behaviour in the current Perl6:
print "Yes r\n" if "0" =~ /0/;
print "Yes s\n" if "0" =~ "0";
prints:
Yes s
It appears that the RE match returns a false value. If I match:
print "Yes r\n" if "1" =~ /1/;
it does print "Yes r". I also tried:
$r= "0"=~/0/;
> match negative multi-byte strings
in perl5, I'd tend to do
m/(?:(?!union).)*/is
or to capture
m/((?:(?!union).)*)/is
I suppose you could use union\b instead of union if you wanted allow
'unions' but disallow 'union'. The general idea is "gobble up each
character that isn't the
On Mon, Oct 07, 2002 at 07:11:08AM -0500, [EMAIL PROTECTED] wrote:
> > match negative multi-byte strings
>
>
> in perl5, I'd tend to do
>
> m/(?:(?!union).)*/is
>
> or to capture
>
> m/((?:(?!union).)*)/is
yeah, I'm not arguing that there isn't a solution available, just that the
so
>From TODO:
Metadata (source line number info, symbol table)
Currently parrot the line number information in parrot is done via
special opcodes, namely setline/getline and setfile/getfile. This is a
good solution when you write an interpreter in parrot, and the line
number information is only
Andy Dougherty:
# Here's a patch that makes misc.c work that way. (This does not fix the
# original trace.c problem at the beginning of this thread.
# trace.c still
# needs to be patched. My original patch is fine for now.)
#
# Also, would it be ok to add some more wrapper functions to
# misc.
At 8:27 PM +0200 10/7/02, Juergen Boemmels wrote:
> >From TODO:
> Metadata (source line number info, symbol table)
>
>Currently parrot the line number information in parrot is done via
>special opcodes, namely setline/getline and setfile/getfile. This is a
>good solution when you write an int
[EMAIL PROTECTED]:
# $i = 0;
# while ($i < 1000) {
# $i++;
# }
#
# With linenumber information enabled this would translate to
# something like this
#
# setline 1
# set I0,0
# LOOP: setline 2
# lt I0, 1000, DONE
# setline 3
# add I0,1
# branch LOOP
# DONE:
On Mon, 7 Oct 2002, Brent Dax wrote:
> I'm working on a patch locally that fixes the long problem (by testing
> at Configure-time for the existence of "long long"), completes the
> feature set of Parrot_sprintf and friends, and adds a PIO_printf and
> PIO_fprintf. It also converts most uses of f
Well, OK, he's not dead, he's just pining for the fjords. And free time. :)
In what I hope is a tradition of transitioning to new Pumpkings and
source managers *before* burnout sets in, Jeff Goff's stepping aside
as Keeper of the Keys and Source.
Stepping up to the job is Steve Fink. Steve's b
Dakkar <[EMAIL PROTECTED]> writes:
> Hi!
> I just found a strange behaviour in the current Perl6:
>
> print "Yes r\n" if "0" =~ /0/;
> print "Yes s\n" if "0" =~ "0";
Here it prints "Yes r" and "Yes s" for perl = 5.6.0, 5.6.1, 5.8.0.
GNU/Linux Redhat 7.2.
-- Johan
On Mon, Oct 07, 2002 at 08:27:29PM +0200, Juergen Boemmels wrote:
> But there must also be a way the higher level languages can assign
> line numbers. Maybe C-like
> #line 1 "foo.c"
> directives are a solution.
> or create dedicated assembler macros
> ..line
> ..file
> (maybe) .column
ooh. nice.
On 20021007203856, Johan Vromans wrote:
> Here it prints "Yes r" and "Yes s" for perl = 5.6.0, 5.6.1, 5.8.0.
Yes, that's precisely the point... the current perl6 doesn't.
(oh, BTW, in the second line perl5 "promotes" the rhs string to a
regexp, doesn't it?)
--
Dakkar -
Real programme
Juergen Boemmels wrote:
>>From TODO:
> Metadata (source line number info, symbol table)
>
> Currently parrot the line number information in parrot is done via
> special opcodes, namely setline/getline and setfile/getfile. This is a
> good solution when you write an interpreter in parrot, and
The current implementation of array.pmc is rather inefficient and
limited - and really slow.
So I rewrote the base routines almost from scratch and have currently a
file named list.c, which I will commit (yep cvs ci, thanks to Dan, Steve
and others, who made this possible) in the next future -
"Brent Dax" <[EMAIL PROTECTED]> writes:
[...]
> # This can be implemented in 2 ways:
> # - Create our own debugging format
> # - Use an already existing one
> # The first way might be more fun, but I think the second one
> # would be better. IMHO we should use DWARF-2. The Mono Project
> # doe
On Mon, 7 Oct 2002, Nicholas Clark wrote:
> On Mon, Oct 07, 2002 at 08:27:29PM +0200, Juergen Boemmels wrote:
> > But there must also be a way the higher level languages can assign
> > line numbers. Maybe C-like
> > #line 1 "foo.c"
> > directives are a solution.
> > or create dedicated assembler
On Mon, 7 Oct 2002, Dakkar wrote:
> print "Yes r\n" if "0" =~ /0/;
> print "Yes s\n" if "0" =~ "0";
>
> prints:
>
> Yes s
>
> It appears that the RE match returns a false value. If I match:
>
> print "Yes r\n" if "1" =~ /1/;
>
> it does print "Yes r". I also tried:
Probably a bug. Is thi
24 matches
Mail list logo
