Autrijus wrote:
Indeed. Somehow I think this makes some sense:
sub Bool eqv (|T $x, |T $y) { ... }
Except that it prevents anyone from ever writing:
multi sub circumfix:| | (Num $x) { return abs $x }
multi sub circumfix:| | (Vec $x) { return $x.mag }
which many
Luke Palmer wrote:
limited access to system settings.
And in those kinds of corporate environments, you're not going to be
working with any code but code written in-house. Which means that
nobody is going to be using Latin-1, and everyone will be using the
ASCII synonyms. What's the
Luke Palmer wrote:
limited access to system settings.
And in those kinds of corporate environments, you're not going to be
working with any code but code written in-house. Which means that
nobody is going to be using Latin-1, and everyone will be using the
ASCII synonyms. What's the
Maeda-san and the list members,
Thank you for raising this issue and sorry for not raising this myself.
On Oct 22, 2005, at 19:42 , Kaoru Maeda wrote:
If we find a lot of yen sign as zip-operator in the standard library,
we have a big question: Give up either Perl6 or Windows. Which do
we
Test::Harness is now at http://svn.perl.org/modules/Test-Harness/
Makes diffing easier for anyone sending patches.
xoxo,
Andy
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Hello all,
So after reading fglock's Perl6::Value/Container modules, some p6l
backtracing and some discussions on #perl6 with Luke and autrijus, I
have arrived at a very early (read: probably wrong) thoughts for the
p6 Object Space.
I see this step as critical in the development of Pugs
On Oct 21, 2005, at 14:11, Roger Browne wrote:
From within a PIR sub or method, how can I detect how many return
values
the caller is expecting?
I'm wondering how to implement a method that will return an error code
if its caller is prepared to receive one, otherwise it will raise an
Dan Kogai wrote:
To make the matter worse, there are not just one yen sign in Unicode.
Take a look at this.
¥ U+00A5 YEN SIGN
￥ U+FFE5 FULLWIDTH YEN SIGN
Tough they look and groks the same to human, computers handle them
differently. This happened when Unicode Consortium decided to make
# New Ticket Created by Nick Glencross
# Please include the string: [perl #37512]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37512
Guys,
call_list.txt lists 'T' and 'L' as being prototypes for passing arrays
On Oct 22, 2005, at 21:02, Bernhard Schmalhofer via RT wrote:
Using registers for passing command line options to a specific runcore
seem hazardous to me. Especially as a 'char *' is put where a 'STRING
*'
is expected.
Yep. This has always been a hack to pass the outfile along.
As
On Oct 22, 2005, at 10:28, Joshua Hoblitt (via RT) wrote:
All revs post r9519 are broken on amd64. r9519 builds OK.
This is an intermdiate step to more final code. I have more already in
the queue and will test it on the 'kua' machine too - greetings to
hawaii ;-) thanks,
leo
Leopold Toetsch [EMAIL PROTECTED] wrote:
On Oct 21, 2005, at 14:11, Roger Browne wrote:
From within a PIR sub or method, how can I detect how many return values
the caller is expecting?
I'm wondering how to implement a method that will return an error code
if its caller is prepared to
I've created pugs/docs/quickref/fears, a list of Perl 6 fears.
Feel free to add your own, or fears you heard about!
If you don't have committer access, ask Autrijus for it, or just reply
to this message.
The current list of fears is:
: Frequently heard Perl 6 fears
:
: Fears end in
On Oct 21, 2005, at 18:07, Will Coleda wrote:
There is now rudimentary support for converting parrot objects to JSON
strings.
+ # generate a JSON representation of a PMC.
+ $S0 = _json( $P0 )
$P0 = new .Array
$P0[0] = $P0
et al, yada yada, ...
Anyway. library/Data/Dumper.imc has the
On Oct 23, 2005, at 17:08, Nick Glencross (via RT) wrote:
Guys,
call_list.txt lists 'T' and 'L' as being prototypes for passing arrays
to nci functions, but no implementation exists in build_nativecall.pl.
This patch provides an implementation, as well as new tests.
I don't think that this
On 10/23/05, Autrijus Tang [EMAIL PROTECTED] wrote:
Dan Kogai wrote:
To make the matter worse, there are not just one yen sign in Unicode.
Take a look at this.
¥ U+00A5 YEN SIGN
￥ U+FFE5 FULLWIDTH YEN SIGN
Tough they look and groks the same to human, computers handle them
On Oct 24, 2005, at 0:07, Jonathan Worthington wrote:
Leopold Toetsch [EMAIL PROTECTED] wrote:
op result_count(out INT)# TODO or some such
I'm guessing TODO means it's not done yet? But I was wondering,
would a more general solution not be to have an op that hands back the
17 matches
Mail list logo
