# New Ticket Created by Brent Dax
# Please include the string: [perl #17817]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17817 >
Inspiration struck me as I was working on bug fixes for Parrot_sprintf's
patch yesterday.
Maybe of interest to some, probably of no interest to most, but this is the
first time I've noticed the use of a perl6 regexp flag in the wild. Or
however "wild" #london.pm on IRC passes for:
Trelane: not really - I think I spent longer debugger
+WWW::UsePerl::Journal than I meant to
/ger/ging
On Wed, 9 Oct 2002, Brent Dax wrote:
[Brent continues to churn out amazing quantities of good stuff]
Overall, it continues to look very good. Unfortunately, the compact-looking
ch=va_arg((va_list)obj->data, char);
gave Sun's compiler indigestion. I had to split it up into the much
more p
On Tue, Oct 08, 2002 at 06:07:09PM -0700, Larry Wall wrote:
> There's this basic rule that says you can't have an operator for both binary
> and postfix, since it's expecting an operator in either case, rather than a
> term (which is how we recognize prefix operators). The one exception I can
> t
On 2002-10-08 at 17:15:06, Larry Wall wrote:
> Seriously, () is just a special token. We could easily have used a
> special token like NULLLIST instead. What does INTERCAL use?
Well, INTERCAL doesn't have lists per se, but it does have arrays, whose
size is set by assignment: the lvalue is the n
Steve Fink wrote:
>
>Oh, and spell Piers Cawley's name correctly! :-)
>
>
DAMN! I new that would happen. Piers, if your out there listening,
forgive me.
Erik
Andy Dougherty:
# Overall, it continues to look very good. Unfortunately, the
# compact-looking
#
# ch=va_arg((va_list)obj->data, char);
#
# gave Sun's compiler indigestion. I had to split it up into
# the much more pedestrian
#
# va_list arg;
# arg = (va_list) obj->data;
#
On Wednesday, October 9, 2002, at 08:49 AM, Erik Lechak wrote:
>> Oh, and spell Piers Cawley's name correctly! :-)
>>
>
> DAMN! I new that would happen. Piers, if your out there listening,
> forgive me.
Did you misspell it a "Bunch" of times?
(Sorry Piers, couldn't resist!)
David
--
Davi
On Wed, 9 Oct 2002, Brent Dax wrote:
> Andy Dougherty:
> # Overall, it continues to look very good. Unfortunately, the
> # compact-looking
> #
> # ch=va_arg((va_list)obj->data, char);
> #
> # gave Sun's compiler indigestion. I had to split it up into
> # the much more pedestrian
> #
>
On Tue, 8 Oct 2002, Larry Wall wrote:
> : but I think the latter is unnatural enough that it deserves parens, so I'd
> : put 'but' above comma (and probably '='), but below just about everything
> : else.
>
> Could perhaps unify with C<..>. Wouldn't hurt for it to be
> non-associative like C<..>
On Wed, 9 Oct 2002, John Williams wrote:
: On Tue, 8 Oct 2002, Larry Wall wrote:
:
: > : but I think the latter is unnatural enough that it deserves parens, so I'd
: > : put 'but' above comma (and probably '='), but below just about everything
: > : else.
: >
: > Could perhaps unify with C<..>.
On Wed, 9 Oct 2002, Nicholas Clark wrote:
: On Tue, Oct 08, 2002 at 06:07:09PM -0700, Larry Wall wrote:
: > There's this basic rule that says you can't have an operator for both binary
: > and postfix, since it's expecting an operator in either case, rather than a
: > term (which is how we recogni
In a message dated Wed, 9 Oct 2002, Larry Wall writes:
> If only we had Unicode editors, we could just force everyone to use
> the infinity symbol where they mean it. It seems a shame to make a
> special case of the .. operator. Maybe we should ... to mean "and so
> on forever":
>
> @a[0...;
On Wed, Oct 09, 2002 at 10:35:32AM -0700, Larry Wall wrote:
> On Wed, 9 Oct 2002, Nicholas Clark wrote:
> : On Tue, Oct 08, 2002 at 06:07:09PM -0700, Larry Wall wrote:
> : Would that mean that three other special cases of postfix .. might exist?
> :
> : 0..; # useful for return 0..;
>
> I bet
On Wednesday, October 9, 2002, at 10:35 AM, Larry Wall wrote:
> Except then we couldn't use it to mean what Ruby means by it, which
> might be handier in real life. (It means to exclude the endpoint,
> so 0...4 is the same as 0..3. But then, that's kind of odd too.)
Uh-oh: my life is gonna s
On Wed, 9 Oct 2002, Brad Hughes wrote:
: Larry Wall wrote:
: [...]
: > Maybe we should ... to mean "and so on forever":
: >
: > @a[0...; 0...:10; 0...:100]
: >
: > Except then we couldn't use it to mean what Ruby means by it, which
: > might be handier in real life.
:
: No more yada-yada-y
In a message dated Wed, 9 Oct 2002, Michael Lazzaro writes:
>
> Uh-oh: my life is gonna suck. I've spent days hunting obscure bugs
> that were caused by a single mistyped character. Now I'll be spending
> days hunting obscure bugs that were caused by a single *pixel*.
>
I've already been the
On Wed, 9 Oct 2002, Andy Dougherty wrote:
> > # Unfortunately, the compact-looking
> > #
> > # ch=va_arg((va_list)obj->data, char);
> > #
> > # gave Sun's compiler indigestion.
> Hmm. Just removing the (va_list) cast makes both Sun's compiler and
> gcc happy. (That's because va_list is
On Wed, 9 Oct 2002, Andy Dougherty wrote:
> diff -r -u parrot-orig/t/src/sprintf.t parrot-andy/t/src/sprintf.t
> + dval = 1.0e6;
> + S = Parrot_sprintf_c(interpreter, "== %g\n", dval);
> + printf("%g %s", dval, string_to_cstring(interpreter, S));
Aargh. I fo
On Wed, Oct 09, 2002 at 02:14:50AM -0400, Tanton Gibbs wrote:
> 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,
On Wed, 9 Oct 2002, Nicholas Clark wrote:
> On Wed, Oct 09, 2002 at 02:14:50AM -0400, Tanton Gibbs wrote:
>
> In order, the other significant compiler warnings I see are:
>
> perlhash.pmc: In function `Parrot_PerlHash_get_pmc_keyed':
> perlhash.pmc:192: warning: passing arg 2 of pointer to funct
In message <[EMAIL PROTECTED]>
Simon Glover <[EMAIL PROTECTED]> wrote:
> This one happens because entry is a HASH_ENTRY*, but get_pmc_keyed is
> expecting a PMC*. However, by this point in the function, we've already
> verified that entry is actually a PMC*, so it should be safe to a
On Wed, Oct 09, 2002 at 04:42:36PM -0400, Andy Dougherty wrote:
> On Wed, 9 Oct 2002, Andy Dougherty wrote:
>
> > diff -r -u parrot-orig/t/src/sprintf.t parrot-andy/t/src/sprintf.t
>
> > + dval = 1.0e6;
> > + S = Parrot_sprintf_c(interpreter, "== %g\n", dval);
> > +
On Wed, 9 Oct 2002, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Simon Glover <[EMAIL PROTECTED]> wrote:
>
> > This one happens because entry is a HASH_ENTRY*, but get_pmc_keyed is
> > expecting a PMC*. However, by this point in the function, we've already
> > verified that
In message <[EMAIL PROTECTED]>
Simon Glover <[EMAIL PROTECTED]> wrote:
> I've just had a quick look at hash.h (which I should have done in the
> first place) and you're quite right. Second attempt at a correct patch
> below.
>
> All tests still pass, but this isn't much comfort, as
On Tue, Oct 08, 2002 at 06:07:09PM -0700, Larry Wall wrote:
> I've always wondered what the ! postfix operator means. The mathematicians
> think they know. :-)
The Ruby folks think they know. They're method name conventions.
>From "Programming Ruby"
Methods that act as queries are often
At 11:28 PM -0400 10/8/02, Erik Lechak wrote:
>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 mor
At 7:42 PM -0700 10/8/02, Steve Fink wrote:
>Thanks, applied.
>
>Who came up with the idea of two-argument ne, anyway? That's kind of
>bizarre.
Definitely bizarre. I think I'd rather not have it, it doesn't make much sense.
--
Dan
--
Yes, you heard right. A cookbook describing stuff that hasn't yet been
designed, for a language that doesn't yet exist. Having flashbacks to
your college years, anyone?
The purpose of the Cookbook is to foster discussion on perl6 OO
concepts, and to start documenting the decisions that are
Robert Spier wrote:
>>This version is in html. I almost have the pod version ready.
>>
>>
>
>So the html is canonical and you're converting it to pod? I'm
>confused.
>
>
I am writing it in my own format. It lets me take notes, write todo
lists, autogenerate the table of contents and g
>I'll see about getting some of the internal structures diagrammed
>better, which is the only place things are a little dodgy, but that's
>otherwise fine.
Simon Wistow <[EMAIL PROTECTED]> dropped me an email and reminded
me about AutoDia http://droogs.org/autodia/
>Now, here's hoping CVS doesn't
>>So the html is canonical and you're converting it to pod? I'm
>> confused.
>I am writing it in my own format. It lets me take notes, write todo
>lists, autogenerate the table of contents and glossary. Then I run it
>through some perl that currently spits out html and almost make pod.
Whatev
core_ops.c(19) : warning C4005: 'CONST' : macro redefinition
C:\Program Files\Microsoft Visual Studio
..NET\Vc7\PlatformSDK\Include\WinDef.h(138) : see previous definition of
'CONST'
jit_cpu.c(20) : warning C4005: 'CONST' : macro redefinition
C:\Program Files\Microsoft Visual Stud
At 10:07 PM -0700 10/9/02, Robert Spier wrote:
> >I'll see about getting some of the internal structures diagrammed
>>better, which is the only place things are a little dodgy, but that's
>>otherwise fine.
>
>Simon Wistow <[EMAIL PROTECTED]> dropped me an email and reminded
>me about AutoDia http
Andy Dougherty:
# You'll probably also want the enhanced sprintf tests (or
# something like
# them.) Currently, the only one that fails for me is the
# %5.3f test, which gives 0.500 in stdio, but
# 0.5 from Parrot.
I finally tracked down this bug. If you look,
35 matches
Mail list logo
