On Thu, Apr 24, 2008 at 1:20 AM, Ph. Marek [EMAIL PROTECTED] wrote:
On Mittwoch, 23. April 2008, Larry Wall wrote:
On Wed, Apr 23, 2008 at 04:03:01PM +0100, Smylers wrote:
: The algorithm for increment and decrement on strings sounds really good,
: however I'm concerned that dealing with
As of r27155 the user_stack data structure has been removed from the core.
After removing stack.ops, the constants STACK_ENTRY_INT,
STACK_ENTRY_FLOAT, STACK_ENTRY_STRING, and STACK_ENTRY_POINTER
aren't used anywhere outside of src/stacks.c . Shall we remove them?
After that, we should be able
Ph. Marek philipp.marek-at-bmlv.gv.at |Perl 6| wrote:
I think that's a can of work, and I'd be +1 on TSa:
If the programmer really wants to decrement 10 to 09 she has
to cast that to Str: (10 as Str)--. So we have 10.HOW === Str
but 10.WHAT === Num Str.
It's behaving as Num ∪ Str,
On 22/04/2008, Jeff Horwitz [EMAIL PROTECTED] wrote:
On Tue, 22 Apr 2008, Donald Hunter wrote:
hi donald!
hm, i thought i committed the fix for this, but apparently not. check out
r334 in the mod_parrot repository.
Great, that fixed my build problem, thanks. I needed to change
I think this is an idea worth exploring, but we'll have to re-survey the
current config step classes carefully before proceeding.
There are certain methods (_init and runstep) which are part of the
public interface each class must implement. _init(), in turn, must
provide a 'description'
On Sun, Apr 13, 2008 at 1:22 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Sat, Apr 12, 2008 at 11:52:44PM +0200, Moritz Lenz wrote:
Conrad Schneiker wrote:
Also, please consider referring people to the Perl 6 wiki (and
any relevant subsections thereof) for more information when
PDD09 lists 3 stacks which are cleaned by the collector, the system
stack, the pmc register stack, and the general/user stack. Do all of
these still exist? If not, this is a small update to make.
--Andrew Whitworth
On Thu, Apr 24, 2008 at 2:10 AM, Patrick R. Michaud via RT
[EMAIL PROTECTED]
On Thu, Apr 24, 2008 at 2:10 AM, Patrick R. Michaud via RT
[EMAIL PROTECTED] wrote:
As of r27155 the user_stack data structure has been removed from the core.
After removing stack.ops, the constants STACK_ENTRY_INT,
STACK_ENTRY_FLOAT, STACK_ENTRY_STRING, and STACK_ENTRY_POINTER
aren't used
From: Patrick R. Michaud via RT [EMAIL PROTECTED]
Date: Wed, 23 Apr 2008 23:10:31 -0700
As of r27155 the user_stack data structure has been removed from the core.
Yay Patrick!
After removing stack.ops, the constants STACK_ENTRY_INT,
STACK_ENTRY_FLOAT, STACK_ENTRY_STRING, and
In response to the messages on the mailing list regarding Perl 6 Fundraising
TPF have been discussing two possible ways to handle donations and fund
allocations for Perl 6.
1. add a new category to the current donation system.
The new category would be called Perl 6 Development, or something
HaloO,
Larry Wall wrote:
On the other hand, 09 has the advantage of still having the numeric
value 9.
Well, I think the canonical representation of of 9 is 9. The mapping
of numeric strings to numbers is N to 1. Is it defined that non-numeric
strings map to NaN or to zero?
But the
On Wed, 23 Apr 2008, Andy Dougherty wrote:
2. There are some casting and type-punning warnings that have, as their
ultimate cause, the STACK_DATAP() macro. Getting rid of the
type-punning warning gives rise to a cast alignment warning.
Looking up a level, the only uses for that macro are
HaloO,
John M. Dlugosz wrote:
If the programmer really wants to decrement 10 to 09 she has to
cast that to Str: (10 as Str)--. So we have 10.HOW === Str
but 10.WHAT === Num Str.
It's behaving as Num ∪ Str, while the declaration Num Str in
juxtaposition means Num ∩ Str.
Hmm? I meant
On Thursday 24 April 2008 12:08:57 Andy Dougherty wrote:
Oops. It won't work because I missed a level of indirection.
-return STACK_DATAP(new_chunk);
That used to return (new_chunk-u.data)
+return new_chunk-u.stdata;
And this returns new_chunk-u.stdata instead.
Oops. I can
On Thu, Apr 24, 2008 at 09:15:15PM +0200, TSa wrote:
I had hoped that WHAT denotes a more specific type than HOW. E.g.
subset ThreeChars of Str where {$_.elems == 3}
my ThreeChars $x = 'xxx';
$x.WHAT; # ThreeChars
$x.HOW; # Str
$x === 'xxx'; # false because type i.e.
HaloO,
Larry Wall wrote:
You are confusing the container with the object. .WHAT and .HOW are
both dynamically typed, and $x.WHAT returns Str, because objects do
not carry subtypes. The container enforces the ThreeChars constraint,
but does not require a ThreeChars object.
Thanks for helping
On Thu, Apr 24, 2008 at 08:10:12PM +0200, TSa wrote:
HaloO,
Larry Wall wrote:
On the other hand, 09 has the advantage of still having the numeric
value 9.
Well, I think the canonical representation of of 9 is 9. The mapping
of numeric strings to numbers is N to 1. Is it defined that
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
... Is it defined that non-numeric
strings map to NaN or to zero?
Zero.
But I think in Perl 6 we're leaning more
toward preserving information than Perl 5 did.
This information being the length of the string I presume.
People have
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
Hmm? I meant Num ∩ Str. This intersection type is a subtype of
Str and Num without type coercion and it beats both in specificity
when it comes to dispatch.
There are methods in Str that are not in Num, and vice versa. A
variable declared as
Larry Wall larry-at-wall.org |Perl 6| wrote:
Neither, probably. You'd get an undef of type Num. Which might or
might not convert to NaN or 0 under various circumstances.
The orthodox documentation has Failure being undef that throws an
exception if you try and get a value from it.
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #53302]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=53302
Short version: Methods should not be automatically entered into
a namespace,
On Thu, Apr 24, 2008 at 03:31:52PM -0500, John M. Dlugosz wrote:
BTW, it will require a new rule in the specification to allow «=« as a
form of pseudo-assignment to declarations. But it has problems with the
list on the RHS anyway.
I don't see why, since there's no list there...and anyway,
On Thursday 24 April 2008 20:31, John M. Dlugosz wrote:
That makes me think of another way to confuse people who don't really
know the difference between numbers and strings:
$x = -100;
$x++;
say $x; # prints -101, not -99.
There's plenty of other ways to confuse people too;
On Thursday 24 April 2008 23:54, smuj wrote:
There's plenty of other ways to confuse people too; try $x with 999 or
1.23e9 :-)
One can even confuse oneself! Forget the dot in 1.23e9 :-)
Cheers,
smuj
--
smuj
([EMAIL PROTECTED])
r27160 eliminates the STACK_ENTRY_(INT|FLOAT|STRING|POINTER) constants
and the cases that were using them in src/stacks.c .
Closing ticket.
Pm
On Thursday 24 April 2008 22:09, Larry Wall wrote:
That makes me think of another way to confuse people who don't really
know the difference between numbers and strings:
$x = -100;
$x++;
say $x; # prints -101, not -99.
Interesting point. At one time we had the increments
Larry Wall larry-at-wall.org |Perl 6| wrote:
The initializer needs to go =inside= the
signature. I think you meant to write
(my int8 ($x, $y)) «=« 127;
It should already parse that way. scope_declarator is a noun,
and nouns may be used on the left side of an infix operator. When
smuj smuj-at-iol.ie |Perl 6| wrote:
Do we still get to keep the current semantics if we specificially declare a
string? e.g.
my Str $x = -100;
$x++;
say $x; # prints -101
my $y = -100;
$y++;
say $y; # prints -99
Cheers,
smuj
I'd vote for that.
As well as a hand full of adjectives.
On Wed Apr 23 18:40:46 2008, [EMAIL PROTECTED] wrote:
There are five configuration step classes where the class's runstep()
method has an internal subroutine called _handle_mswin32(). These
classes are:
config/auto//crypto.pm
config/auto//gettext.pm
config/auto//gmp.pm
On Thu, 2008-04-24 at 19:55 -0700, James Keenan via RT wrote:
Please see patch attached. It turned out that config/auto/opengl.pm
didn't quite conform to the pattern, so I left it unchanged.
Other than having a Darwin case, how is it different than the pattern?
Also, the implementation of
On Thu, 24 Apr 2008 20:48:34 -0700
Geoffrey Broadwell [EMAIL PROTECTED] wrote:
Also, the implementation of C_add_to_libs is a little wordy. How's
this?
sub _add_to_libs {
my ($self, $args) = @_;
croak _add_to_libs() takes hashref unless ref($args) eq 'HASH';
my $os
On Thu, 2008-04-24 at 21:53 -0700, Mark Glines wrote:
On Thu, 24 Apr 2008 20:48:34 -0700
Geoffrey Broadwell [EMAIL PROTECTED] wrote:
my $platform = $os =~ /mswin32/i $cc =~ /^gcc/i ? 'win32_gcc' :
$os =~ /mswin32/i ? 'win32_other' :
32 matches
Mail list logo
