> Hello!
>
> Recently I was coding Perl 5 and quite often I had to change
> interpolated strings or C to C or .
>
> I began to wonder, if qq strings couldn't allow sprintf-like
> formatting directly.
>
> I could imagine an \F escape sequence with the following syntax:
>
> :'\F' printf-form
> Hello,
>
> the Linux Standard Base would like to include PERL into the standard, i.e.
> a LSB conform package may use PERL without the need to pack it itself, but
> PERL lacks a specification.
>
> What would be enough is a subset of the perl language that can be tested
> to be portable across
Any thought on when PerlHashes will be able to allow us to iterate over the
keys? Possibly do things like:
new P0, .PerlHash
set P0["skeleton"], value
set P0["master"], value
set P0["Odin'sBro"], value
set P0["USPO4,314,236"], value
set P0["burro"]
At 1:30 PM +0200 6/14/03, Leopold Toetsch wrote:
PMCs are different. Currently many opcodes with PMCs are defined like:
B(inout PMC, in PMC)
This is plain wrong. If the LHS PMC doesn't exist yet, you can't
call its add vtable method (The implementations is
$1->vtable->add(...)).
You're right.
Here are some notes from the experimental parrot wiki
http://www.vendian.org/parrot/wiki/
A list of parrot build-time files (on x86).
Configure.pl creates Makefiles
./Makefile
./classes/Makefile
./docs/Makefile
./languages/Makefile
./languages/befunge/Makefile
./languages/bf/Makefile
./l
> To the wider community: BTW. For fun, I used imcc to convert the .imc to
> a .pasm file, but them imcc couldn't run this file (trouble with
> labels). Should this have worked?
In PASM mode the whole file is compiled at once. IMCC as well as
assemble.pl has troubles with duplicate
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [perl #22706]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22706 >
Running imcc -t or parrot -t over an invoke instruction causes the programs
to s
At 4:56 PM +0200 6/15/03, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
... The non-JIT version compiles and builds just
fine (including IMCC) but the JIT version does throw some errors.
This isn't unexpected, unfortunately. (Sorry 'bout the extra work on
the JIT, guys)
JIT/i38
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> ... The non-JIT version compiles and builds just
> fine (including IMCC) but the JIT version does throw some errors.
> This isn't unexpected, unfortunately. (Sorry 'bout the extra work on
> the JIT, guys)
JIT/i386 is working fine.
leo
Nick Glencross <[EMAIL PROTECTED]> wrote:
> To the wider community: BTW. For fun, I used imcc to convert the .imc to
> a .pasm file, but them imcc couldn't run this file (trouble with
> labels). Should this have worked?
In PASM mode the whole file is compiled at once. IMCC as well as
assemble.pl
Edwin Steiner <[EMAIL PROTECTED]> writes:
> "Leave some --\Fs60{space for this $interpolates string}--."
I'm sorry, this should be:
> "Leave some --\F60s{space for this $interpolates string}--."
Hello!
Recently I was coding Perl 5 and quite often I had to change
interpolated strings or C to C or .
I began to wonder, if qq strings couldn't allow sprintf-like
formatting directly.
I could imagine an \F escape sequence with the following syntax:
:'\F' printf-format-without-% '(' expr
Clinton A. Pierce wrote:
If you want something to play with, update the
languages/BASIC/compiler tree and run the chess program.
This is an amazing milestone in the parrot (and BASIC) development
cycle. Well done!
To the wider community: BTW. For fun, I used imcc to convert the .imc to
a .pas
13 matches
Mail list logo
