On Tue, Apr 11, 2006 at 03:49:45AM +0200, herbert breunung wrote:
: hello perlisticers
:
: (my first post)
: i read in the perl6 book second edition something called
:
: /Integer context/ and /Numeric context/
:
: Ican understand the difference but since nowhere in the synopses i read
: a word
Author: larry
Date: Mon Apr 10 21:39:58 2006
New Revision: 8645
Modified:
doc/trunk/design/syn/S02.pod
Log:
Outlawed 42. (but inlawed .42)
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod
HaloO,
I'm unsure what the outcome of the recent long dot discussions is
as far as the range operator is concerned. Since the whole point
of the long dot is to support alignment styles the following cases
shouldn't mean different things:
foobar #0 single call to foobar (OK, that is
# New Ticket Created by Will Coleda
# Please include the string: [perl #38896]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=38896
There are many math ops that work on Float PMCs but not Integer PMCs.
e.g.:
% cat
# New Ticket Created by jerry gay
# Please include the string: [perl #38897]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=38897
if slash replacement mode is active (as set in
config/gen/makefiles.pm) during
On Apr 7, 2006, at 19:38, Nicholas Clark wrote:
-STRING *fill = CONST_STRING(interpreter, info-flags
FLAG_ZERO ? 0 : );
I think that this change is masking the true bug,
No. Above replaced line was definitely bogus. CONST_STRING is a macro
that takes *one* string constant and
On Tue, Apr 11, 2006 at 12:41:30PM +0200, TSa wrote:
: I'm unsure what the outcome of the recent long dot discussions is
: as far as the range operator is concerned.
.. is always the range operator. The dot wedge just has a discontinuity
in it there. I can't think of any wedgey applications
{ p6i added ... this has turned into an interesting design discussion }
On Wed, Apr 05, 2006 at 03:54:51PM +0200, Leopold Toetsch wrote:
On Tue, Apr 04, 2006 at 11:42:36AM -0700, Chip Salzenberg wrote:
I've done some [more] reading up on value types. [...]
Parrot 1.0 will _not_ have native
Folks,
I found this when I was playing w/ pugs.
pugs { $^x }.(42)
42
pugs { my $z; $^x }.(42)
*** Undeclared variable: $^x
at interactive line 1, column 10-14
So far as I see s06, there's nothing wrong w/ the statement above. I
just want to make sure this is not a perl6 feature.
I
On Tue, Apr 11, 2006 at 07:05:33AM -0700, Will Coleda wrote:
P1 = new .Float
P1 = 123
The assignment of 123 autoconverts the float to an integer, which
doesn't support the 'exp' method that's defined in the Float pmc.
(Change the 123 to 123. and it works fine.)
Given the morphing
Author: allison
Date: Tue Apr 11 13:28:33 2006
New Revision: 12178
Added:
trunk/docs/pdds/clip/pddXX_events.pod
trunk/docs/pdds/clip/pddXX_threads.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Very, very early drafts of the threads and events
On Tue, Apr 11, 2006 at 06:15:32PM +0200, Leopold Toetsch wrote:
On Apr 7, 2006, at 19:38, Nicholas Clark wrote:
-STRING *fill = CONST_STRING(interpreter, info-flags
FLAG_ZERO ? 0 : );
I think that this change is masking the true bug,
No. Above replaced line was
On Tue, Apr 11, 2006 at 08:30:09PM +0100, Nicholas Clark wrote:
On Tue, Apr 11, 2006 at 07:05:33AM -0700, Will Coleda wrote:
P1 = new .Float
P1 = 123
The assignment of 123 autoconverts the float to an integer, which
doesn't support the 'exp' method that's defined in the Float pmc.
On Mon, Apr 10, 2006 at 10:41:50AM +0100, Jonathan Worthington wrote:
Patrick R. Michaud [EMAIL PROTECTED] wrote:
At any rate, I suspect pbc_merge is the culprit.
If you have any simple(-ish ;-) test cases that demonstrate the particular
issue, I'll probably have a little time in the next
On Apr 11, 2006, at 22:48, Nicholas Clark wrote:
On Tue, Apr 11, 2006 at 06:15:32PM +0200, Leopold Toetsch wrote:
No. Above replaced line was definitely bogus. CONST_STRING is a macro
that takes *one* string constant and it has likely to be own it's own
line.
Ah. Thanks for the
On Apr 11, 2006, at 23:15, Patrick R. Michaud wrote:
Just to add a me too of sorts -- I didn't really notice it when
most everything was using Perl* PMCs, but now that we've separated
things out into base types the behavior seems very odd, unexpected,
and somewhat undesirable.
This isn't
On Apr 11, 2006, at 21:30, Nicholas Clark wrote:
I can see value in a type .Number, which changes internal
representation and
vtable as and when necessary, but I'd still expect it to report
Number
when asked what type it is
[ ... ]
Was this built in morphing the cause of the problems
Dan Kogai wrote:
I found this when I was playing w/ pugs.
pugs { $^x }.(42)
42
pugs { my $z; $^x }.(42)
*** Undeclared variable: $^x
at interactive line 1, column 10-14
So far as I see s06, there's nothing wrong w/ the statement above. I
just want to make sure this is not a perl6
18 matches
Mail list logo
