On Jul 21, 2006, at 1:12 PM, Mr. Shawn H. Corey wrote:
Chris Dolan wrote:
This would be a good entry for the FAQs for a cage cleaner.
If you're collect questions for the FAQ, here are some Andy Lester
answered for me:
I'm not, actually. :-(
Could you do one of the following, in order of p
# New Ticket Created by Will Coleda
# Please include the string: [perl #39905]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39905 >
Once a .tg file is compiled to a .pir file, any errors in the
embedded PIR are reported
Can we discuss this on list a bit?
On Jul 21, 2006, at 5:07 PM, [EMAIL PROTECTED] wrote:
Author: duff
Date: Fri Jul 21 14:07:00 2006
New Revision: 13424
Added:
trunk/docs/art/
Log:
place for parrot articles
--
Will "Coke" Coleda
[EMAIL PROTECTED]
On Friday 21 July 2006 11:43, Leopold Toetsch wrote:
> Without futher looking - you have to replace a lot of 'p's (some structure)
> with 'J' (the Interpreter* interp structure). E.g.
>
> .store_nci_func( 'Parrot_readbc', 'ppt' )
>
> =>
>
> .store_nci_func( 'Parrot_readbc', 'pJt' )
I'm not co
[EMAIL PROTECTED] writes:
> s/loop/repeat/ for test-after loops
Yay! That makes things very clear, with different things looking nicely
different.
Smylers
Author: larry
Date: Fri Jul 21 12:52:51 2006
New Revision: 10350
Modified:
doc/trunk/design/syn/S04.pod
Log:
s/loop/repeat/ for test-after loops
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.
On Fri, Jul 21, 2006 at 03:04:06PM -0400, Mr. Shawn H. Corey wrote:
> Determining if your C compiler is actually gcc.yes.
> Determining if your C compiler is actually Visual C++...no.
> Enabling optimization...n
In a message dated Fri, 21 Jul 2006, Ruud H.G. van Tol writes:
Larry Wall schreef:
Maybe we should just make statement modifiers
uppercase and burn out everyone's eye sockets. :)
Or maybe
{
}.
while $x ;
Actually, can't that be made to work already (already by the language
spec, not
Larry Wall schreef:
> Maybe we should just make statement modifiers
> uppercase and burn out everyone's eye sockets. :)
Or maybe
{
}.
while $x ;
--
Groet, Ruud
On Fri, Jul 21, 2006 at 02:12:57PM -0400, Mr. Shawn H. Corey wrote:
> Chris Dolan wrote:
> > 1. Do I need root privileges to install Parrot? Do I need it for Cage
> > Cleaners?
>
> You don't even need root at all. You can build in a local directory and
> not install.
In fact, for those who are d
Hi,
I ran `perl Configure.pl` and I have some questions about its output.
First:
Determining if your C compiler is actually gcc.yes.
Determining if your C compiler is actually Visual C++...no.
Enabling optimization..
Am Freitag, 21. Juli 2006 20:08 schrieb chromatic:
> On Friday 21 July 2006 00:57, Leopold Toetsch wrote:
> > (You could use 'pIt' and 'pIp' signatures too, then the STRING* result of
> > the 'const_string' would be wrapped into a ManagedStruct PMC).
>
> I don't see documentation for the S or I par
Author: audreyt
Date: Fri Jul 21 11:40:37 2006
New Revision: 10348
Modified:
doc/trunk/design/syn/S02.pod
Log:
* S02: rodi++ pointed out a nit:
"say q<< <> >>"
should print " <> " not "<>".
Modified: doc/trunk/design/syn/S02.pod
Chris Dolan wrote:
> On Jul 21, 2006, at 9:48 AM, Jonathan Rockway wrote:
>
>>> I have downloaded the icu4j_3_4_4.jar but have no idea what to do with
>>> it. Could someone please help?
>>>
>> You'll want to get icu4c (icu for C), not icu4j (for java). If you
>> get the tgz C version, just tar xz
On Friday 21 July 2006 00:57, Leopold Toetsch wrote:
> This can't work for several reasons:
>
> 1) the NCI call signatures don't match the C functions' args:
>
> .store_nci_func( 'const_string', 'ppt' )
>
> should be: 'SIt' (return STRING*, interp & C-cstring args)
>
> .store_nci_func
On Fri, Jul 21, 2006 at 12:07:52PM -0500, Jonathan Scott Duff wrote:
: Or just give them some sort of syntactic marker ... I know!
:
: loop {
: ...
: }
: :while $loopy;
:
: eat :if $hungry;
: go_postal :when $aggravation > 10;
: .sleep :until .rested;
:
: *Everybo
On Jul 21, 2006, at 9:48 AM, Jonathan Rockway wrote:
I have downloaded the icu4j_3_4_4.jar but have no idea what to do
with
it. Could someone please help?
You'll want to get icu4c (icu for C), not icu4j (for java). If you
get the tgz C version, just tar xzvf it, cd source; ./configure;
m
On Thu, Jul 20, 2006 at 10:18:57AM -0700, Larry Wall wrote:
> It ain't easy. Maybe we should just make statement modifiers uppercase
> and burn out everyone's eye sockets. :)
Or just give them some sort of syntactic marker ... I know!
loop {
...
}
:while $loopy;
eat :if
On Thu, Jul 20, 2006 at 05:03:32PM +0100, Smylers wrote:
: Markus Laire writes:
:
: > S04 seems to say that a style like this can't be used by
: > perl6-programmers:
: >
: > loop
: > {
: >...
: > }
: > while $x;
: >
: > I like this style, as it lines up both the keywords and the curlies.
:
I have downloaded the icu4j_3_4_4.jar but have no idea what to do with
it. Could someone please help?
You'll want to get icu4c (icu for C), not icu4j (for java). If you get
the tgz C version, just tar xzvf it, cd source; ./configure; make; make
install. Note that most Linux distros have p
Hi,
I am trying to install Parrot and the README file has this:
You'll need a C compiler, a linker and a make program of course. If you
will be linking with the ICU library you have to download and install it
before configuring Parrot.
Get it from http://www-306.ibm.com/software/globalization/ic
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 21 Jul 2006 00:24:13 -0700
chromatic wrote:
> Here's what I don't understand. Why is there talk of a stack to keep
track of
> various flow control constructs? Doesn't a CPS system use a linked list
of
> continuations to h
On 7/20/06, Smylers <[EMAIL PROTECTED]> wrote:
Markus Laire writes:
> S04 seems to say that a style like this can't be used by
> perl6-programmers:
>
> loop
> {
>...
> }
> while $x;
>
> I like this style, as it lines up both the keywords and the curlies.
As of yesterday you can get very c
There are 3 problems with the test:
%x takes an *unsigned int*, the conversion from -1 to UI can use internally an
arbitrary (and unspecced, arch-specific) amount of bits.
The test is wrong for 64-bit architectures.
And finally: trailing whitespace in tests is *bad*.
leo
Am Freitag, 21. Juli 2006 07:53 schrieb chromatic:
> Should this code work? I think so.
This can't work for several reasons:
1) the NCI call signatures don't match the C functions' args:
.store_nci_func( 'const_string', 'ppt' )
should be: 'SIt' (return STRING*, interp & C-cstring args
chromatic wrote:
Here's what I don't understand. Why is there talk of a stack to keep track of
various flow control constructs? Doesn't a CPS system use a linked list of
continuations to handle normal flow control? If that works there, why not
another linked list of continuations to handle
26 matches
Mail list logo
