Hello,
Some time ago, I announced I would be writing a paper on the
architecture of Parrot. The paper will be about 10 pages (I think, at
this point), so there will be quite a high level of abstraction in order
to be able to fit all important info. (so no "class" diagrams, if one
could even s
Hi, attached a patch with a start on the implementation of flush.pir
Note that ParrotIO.pmc doesn't seem to have a method to find out what
mode it is opened in, so that check cannot be done.
regards,
kj
Will Coleda (via RT) wrote:
# New Ticket Created by Will Coleda
# Please include the st
hi,
attached is a patch that adds the new ".lex" syntax. The description is
copy/paste from PDD20.
regards,
klaas-jan
--- imcc/docs/syntax.pod2005-12-05 19:49:30.0 +0100
+++ imcc/docs/syntax2.pod 2005-12-05 20:15:53.0 +0100
@@ -207,6 +207,25 @@
them with commas:
hi,
if I understood correctly, the global storage is implemented as a hash
table.
If so, will it be possible to load this global hash table in a P register?
So, for example, are there any plans to support this:
$P0 = get_globals # put a reference to the global storage into
register $P0
Leopold Toetsch wrote:
On Dec 5, 2005, at 21:58, Klaas-Jan Stol wrote:
hi,
if I understood correctly, the global storage is implemented as a
hash table.
If so, will it be possible to load this global hash table in a P
register?
It is possible right now. See the introspection interface
Hi,
I get some strange behaviour in the attached code snippet.
The problem is with the lines marked with a '*'. If the global 'r' is
stored into $P0,
and in the second marked line it is called, the output of the print
statements furhter below
is:
Lua_Proto_2_0
2
instead of the expected
1
2
Hi,
I'm wondering, is there a PDD about Thread implementation in Parrot? I
searched the list archive, and found a lot of info. Dan even mentioned
writing a PDD on the subject, but I havent' been able to find it.
Thanks,
klaas-jan
Hi,
As you know, I'm currently busy writing a paper on the architecture of
Parrot, and during my attempt to describe the exception sub-system,
something came to mind. I'm not sure if the event system is fully
operational (I thought it was already implemented), but I do know the
plan was to che
Hi,
As you know, I'm currently busy writing a paper on the architecture of
Parrot, and during my attempt to describe the exception sub-system,
something came to mind. I'm not sure if the event system is fully
operational (I thought it was already implemented), but I do know the
plan was to che
more work.
I hope it's worthwhile to read. I'll be finishing it this weekend. If
you read it and think to see incorrect information, please inform me.
(most information is from mailing lists, docs and Perl6 essentials 2nd
ed., so some info could be out-of-date)
Kind regards,
Klaas-Jan Stol
ee what kind of code the Lua compiler should more or less be generating.
Kind regards,
Klaas-Jan Stol
Hi,
I'm trying to implement some functions into the Lua PMCs, but I'm having
trouble to compile them.
I want to add a clone method to the LuaNil PMC (which should extend
Null.pmc, not None.pmc, as it does currently; changed that already)
However, I get the following error:
luanil.c:343: er
Joshua Hoblitt wrote:
On Thu, Jan 12, 2006 at 04:53:26PM +0100, Leopold Toetsch wrote:
Klaas-Jan Stol wrote:
Hi,
I'm trying to implement some functions into the Lua PMCs, but I'm having
trouble to compile them.
I want to add a clone method to the LuaNil PMC (which sho
.const .LuaNumber n = "12.34"
I presume LuaNumber doesn't have new_from_string (Float hasn't either).
Attached is a patch that implements new_from_string() for LuaNumber.
In my opinion it's handy to say:
.const .LuaNumber n = "12.34"
kind regards,
klaas-jan
--- languages/lu
st;
-}
-
-}
-
-/*
-
-=back
-
-=head1 AUTHORS
-
-Original code by Klaas-Jan Stol.
-
-=cut
-
-*/
-
+/*
+Copyright: 2005 The Perl Foundation. All Rights Reserved.
+$Id: luanil.pmc 10933 2006-01-06 01:43:24Z particle $
+
+=head1 NAME
+
+classes/luanil.pmc - Lua Nil
+
+=head1 DESCRIPTION
this patch changes the behaviour of the LuaTable PMC.
changes have to do with the reference semantics that PMCs have, and
LuaTables should not have.
Setting and getting a value now will set (and get) a copy of the value.
Clone() returns a reference to itself, as clone() should be used for
reg
hi,
I have 2 questions wrt PIR parameter notation and usage.
I'm not quite sure how I should specifiy the flags when using
get_params, instead of the .param notation.
according to PDD03, flag "3" is for specifiying slurpy parameters.
Should I type:
get_params "(3)", $P0
to say $P0 is a s
Hi,
since yesterday, Parrot breaks during compiling, with the following output:
c++ -o miniparrot -L/usr/local/lib -Wl,-E compilers/imcc/main.o \
-Wl,-rpath=/home/klaas/parrot/blib/lib -L/home/klaas/parrot/blib/lib
-lparrot -lnsl -ldl -lm -lcrypt -lutil -lpthread -lrt -lgmp
src/null_config.o
Klaas-Jan Stol wrote:
Hi,
since yesterday, Parrot breaks during compiling, with the following
output:
c++ -o miniparrot -L/usr/local/lib -Wl,-E compilers/imcc/main.o \
-Wl,-rpath=/home/klaas/parrot/blib/lib -L/home/klaas/parrot/blib/lib
-lparrot -lnsl -ldl -lm -lcrypt -lutil -lpthread
Hi,
I tried to index aggregates using several types of keys (that is,
several types of values), and it seems only string and integer values
can be used as keys. A quick look at the source in
compilers/imcc/symreg.c confirms this, there is no case for 'N' values
(and a test makes Parrot say bu
Matt Fowles wrote:
Klaas-Jan~
On 1/20/06, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
Hi,
I tried to index aggregates using several types of keys (that is,
several types of values), and it seems only string and integer values
can be used as keys. A quick look at the source in
compiler
Matt Fowles wrote:
LuaNil Morphing
Klaas-Jan Stol proffered a patch which changed LuaNil from a singleton
and made it morph to other Lua types when asked. Warnock applies.
Actually, François Perrad applied this patch, but I think he only sent a
reply to me.
<http://xrl
Bernhard Schmalhofer wrote:
Will Coleda schrieb:
There was an agreement on 5.6.1 a few weeks back on IRC, if I recall
correctly, I haven't heard anything about 5.8.
This change was made here:
r11744 | bernhard | 2006-02-26 05:55:39 -0500 (Sun, 26 Feb 2006) | 7
lines
Configuration:
- Sp
hi,
if I understand correctly, the :immediate pragma makes the sub which has
this pragma run immediately after parsing (well, at least before running
the program)
Suppose I have this code:
.sub loadstuff :immediate
# load stuff
.end
.sub main
dostuff( )
end
.
Hi,
I couldn't find any functionality to reset a coroutine. Sometimes you want
to reset a coroutine, so it starts at the beginning of the sub body, but
there doesn't seem to be any method to do that. Am I overlooking something?
Thanks,
klaas-jan
Coroutine, but it seems to me it shouldn't be
too hard.
Kind regards,
klaas-jan
On 5/29/06, Elizabeth Mattijsen <[EMAIL PROTECTED]> wrote:
At 11:04 PM +0200 5/29/06, Klaas-Jan Stol wrote:
>I couldn't find any functionality to reset a coroutine. Sometimes you
want
>to res
hi,
I was investigating a possible implementation of the "reset" method for
coroutine.pmc, but I encountered the following:
if the coroutine is called more times than the coroutine ".yield()s", it
segfaults
example:
.sub main :main
.local int result
.local pmc cor
cor = global "_foo
Hi,
I had a look at this, but I'm not that good at Perl, and regular
expressions. However, I found where things go wrong, so someone who
really groks REs may fix it.
THe problem is (well, at least I think it is) at about line 440 in pmc2c.pl
sub parse_pmc {
my $code = shift;
my $signa
Leopold Toetsch wrote:
Recently on IRC:
@woggle> leo: So, for read-only PMC variants, I'm presuming that it's okay
to have the read-only
variants have their own type number and type name (like was
done for ConstSArray)...
My 2 c:
A distinct type number would cause e.g. dif
hello,
yesterday I had a look at why tcl does not build on windows. Although I
haven't been able to fix it, I'd like to share the issues I found, so
you don't have to look for it yourself.
there were several problems with the makefile
line 123:
ops: src\binary.o , should be binary$(O)
this
Hi,
I tried to write a little script that checks for the copyright notice
and updates it if necessary.
THere are some comments on what should be done (SVN date comparing and
stuff.
hope this helps,
kjs
#
# Start of a script to recursively process all files in a directory to change
the copyri
Matt Diephouse wrote:
Allison Randal via RT <[EMAIL PROTECTED]> wrote:
> PMC Class name IDs ... will require a dot in front
My preference is to eliminate the dot in classname IDs. Lodge your
objections now, before it's made fact in 0.4.9.
Allison
I actually prefer the dot. I don't like the p
I like the idea. Write up a more complete proposal and we'll all
review it. A few thoughts:
- The same mechanism could be used to implement Perl 6 sub wrapping,
so keep that in mind as you're thinking through the implementation
options. Names like "trace_sub" may be too specific to one par
hello,
I'm trying to set up a test harness for languages/PIR
I did the following:
1. added a file lib\Parrot\Test\PIR.pm
(there are others, like Punie.pm).
I changed this file a bit, so it uses pir.pbc as compiler (I copied
the file from Punie.pm, and changed the compiler from punie.pbc t
This will require either an update to lib/Parrot/Test.pm, or that you
use a different language name for the language arg and module. I
recommend the latter, e.g. "PIR_PGE". You won't need to change the
language DIR or the compiled .pbc you're using.
Regards.
On Jan 30,
hello,
Parrot has 2 categories of registers: PASM registers, which are of the
form [S|N|I|P] (which is kinda odd, if only regs 0-31 are
available) and PIR registers, which are formed like: $[S|N|I|P]+
In the old days, this distinction was necessary for the register
allocator to translate PIR
hi,
IIRC, IMCC started as a kind of pre-processor for PASM, in other words,
it allowed more readable shortcuts for several constructs. Eventually,
everything was translated to pure PASM, that is, 1 long list of real
Parrot instructions (no .sub/.end blocks etc).
At some point, IMCC was merge
attached a patch that makes ./parrot --version respond copyright
2001-2007, instead of 2001-2006.
regards,
kjs
Index: compilers/imcc/main.c
===
--- compilers/imcc/main.c (revision 16864)
+++ compilers/imcc/main.c (working copy)
@@ -
hi,
attached are 2 files: a script that checks all files for the Last
Changed Date according to SVN, and updates the file if its year >
copyright notice in the file. I'm not very good with Perl, so it might
be badly programmed... However, it only needs running once.
The 2nd file is a test, a
lows PASM instructions,
+not PIR instructions.
+
+
+ emit:
+".emit" nl
+labeled_pasm_instr*
+".eom"
+
+NOTE: the macro definition is not complete, and untested.
+This should be fixed. For now, all characters up to but not
+including ".endm" are 'mat
hello,
Some details of the Parrot calling conventions are a bit unclear. For
the languages/PIR parser implementation, I'd like to check on this
order, instead of postponing the check this in a later phase. My guess
is that the actual checking for mismatches is done in Parrot during
runtime, b
hi,
I noticed the file calling_conventions.pod misses the sub pragmas
:postcomp (and I understood this is the same as :immediate) and
:outer(sub).
This patch adds these pragmas.
regards,
kjs
Index: docs/imcc/calling_conventions.pod
===
Allison Randal wrote:
James Keenan wrote:
Which leads to my next questions:
Given a knowledge of a dynamic language (I believe there's one called
Perl 5), what is the trajectory for learning PIR?
Is there any tutorial in the docs?
There's docs/imcc/syntax.pod. Not a tutorial, but a decent
chromatic wrote:
On Wednesday 07 February 2007 08:33, Klaas-Jan Stol wrote:
attached a patch for pirgrammar.pod and its html variant.
Keeping this HTML in the repository sucks. Is there a possibilty that we
could generate it automatically? What's preventing us from doing so
hi,
attached an update for ASTGrammar.tg for languages/PIR
In order to print the past tree to screen, set 'target' to 'past' in
pirc.pir. Currently, it is set to 'parse' in order to pass the tests.
regards,
klaas-jan
Index: languages/PIR/lib/ASTGrammar.tg
=
hi,
attached a patch for docs/imcc/syntax.pod
fixing:
* typo, changing eamples in examples
* added ", respectively" to description of binary/hex numbers
* added syntax description for slices:
= [ ]
where is one of:
..
..
..
Also, I added references to 2 files to the slicing part. Please
hi
attached a patch for languages/PIR fixing:
* added optional "utf8:" encoding specifier (according to
docs/imcc/syntax.pod)
* fixed support for binary and hex. numbers
* added test for these changes.
regards,
klaas-jan
Index: languages/PIR/lib/pir.pg
hi,
attached a patch for lang/PIR fixing:
* add command line options to specify the kind of output:
- parse only (used for tests currently)
- PAST
- PIR
- parse and dump parse tree.
(I stole the code from tge.pir)
regards,
kjs
Index: languages/PIR/pirc.pir
===
hi
attached a patch for lang/PIR fixing:
* extended TGE, but far from complete
* minor changes in .pg file
regards,
kjs
Index: languages/PIR/lib/ASTGrammar.tg
===
--- languages/PIR/lib/ASTGrammar.tg (revision 16957)
+++ languages/P
hello,
It was discussed before, but I'm not sure what was the result; PAST-pm
only allows a PAST::Block node to be returned from transform (ROOT).
However, in languages/PIR, the top level construct is a compilation
unit, which may be an include statement. An include statement should not
be en
hi,
attached a patch for languages/PIR, fixing:
* changed PIRGrammar into PIR::Grammar (changes many files)
* updated pirgrammar.pod
* updates to ASTGrammar.tg
regards,
kjs
Index: languages/PIR/docs/pirgrammar.pod
===
--- languages
hi,
* attached a patch that implements better macro parsing
* begin of better heredoc parsing,but not finished yet.
* added test for macro parsing
regards,
klaas-jan
Index: languages/PIR/examples/macro2.pir
===
--- languages/PIR/ex
hi,
attached a patch for the PGE implementation of the Lua parser (lua.pg).
fixing:
* make rule match longest identifiers, not keyword-prefixed
identifiers (like "for" in "format")
* fix parameter list rule
* all examples in the lua distribution (in the test directory) can be
parsed correct
attached a patch for fixing
* some things for parsing PASM instructions correctly
* minor updates to pir.pg
regards,
kjs
Index: languages/PIR/lib/pasm_args.pg
===
--- languages/PIR/lib/pasm_args.pg (revision 17016)
+++ languages/PIR/
hi,
I was browsing the TODO list for some low hanging fruit, and saw a
request for updating PDD20.
Attached a patch that adds a description of get_outer() according to
t/op/lexicals.t to PDD20.
regards,
klaas-jan
Index: docs/pdds/pdd20_lexical_vars.pod
==
hi,
I made some small updates to faq.pod, regarding TODO ticket #41312:
[TODO] - Docs - update FAQ.
updating:
* updated languages section
* updated PASM to PIR usage
* removed VERSION section as suggested in the ticket.
It does NOT fix:
* I left Parrot/Perl6 in, I'm not sure if it should be
hi,
I was working on a test for addmethod op (ticket #39196: [TODO] tests -
need to test addmethod) and
tried this:
.sub main :main
# this works:
hello()
# while this does not:
$P0 = find_name "hello"
$P0()
.end
.sub hello :anon
print "Hello world!\n"
.end
My question is
hi,
attached a new patch, replacing the other one from 2/17.
kjs
Index: languages/PIR/lib/pasm_args.pg
===
--- languages/PIR/lib/pasm_args.pg (revision 17016)
+++ languages/PIR/lib/pasm_args.pg (working copy)
@@ -1,4 +1,4 @@
-grammar
hi
attached a patch for languages/PIR, fixing:
* added unique_reg to allowed flags for parameters
* updated pirgrammar.pod
* removed pirgrammar.html (can be generated)
* minor fixes for pir.pg (both syntax and comments, now in POD format)
regards,
kjs
Index: languages/PIR/docs/pirgrammar.pod
===
so, if we decide that anything starting with a dot that doesn't have
parens is a type, I could write:
$I0 = typeof $P0
if $I0 == .Foo goto bar
You can do that already.
Klaas-Jan Stol wrote:
A dot also indicates that this is not pure PASM, but rather PIR.
Except that the dot is req
I'm not sure how to respond on TODO tickets, any pointers would be
appreciated.
Meanwhile, I'll just compose an email, like this one.
Ticket:
#37542: [TODO] core - document behavior of multiple :load subpragmas in
same compilation unit
states:
the behavior of multiple subroutines marked with
hi,
currently there are some deprecated ops, as listed in:
http://www.parrotcode.org/docs/ops/var.html
they are not listed in DEPRECATED.pod
This is not the first time some ops are deprecated, and will probably
not be the last time before the 1.0 release.
Is it a good idea to add a check to th
hi,
attached a patch for the Lua grammar file for PGE (lua.pg).
fixing:
* reorganized some rules w.r.t. "do end"
* rule instead of "..."
* fixed table constructor rules (they now work correctly) -- stolen from
lua51.pg
regards,
kjs
Index: languages/lua/src/lua.pg
==
hi,
I've been playing with NCI calls and more fun (embedding a Parrot, that
runs a PIR program, which invokes a C function, that then invokes a PIR
callback function).
As a result, I added a simple example to PDD16. I didnt' put too much
work in it (there are many more places that could be i
hi,
attached an update for languages/PIR/docs/pirgrammar.pod
fixing:
0.1.3
*
Updated short sub invocation for NCI invocations.
*
Added an example for |.globalconst|.
*
Added some remarks at section for Macros.
*
Added some remarks here and there, and fixe
hi,
attached a patch updating DEPRECATED.pod.
it adds the deprecated ops from http://www.parrotcode.org/docs/ops/var.html
(ops: store_global and friends)
regards,
kjs
Index: DEPRECATED.pod
===
--- DEPRECATED.pod (revision 17165)
++
James Keenan via RT wrote:
On Fri Feb 23 13:44:22 2007, [EMAIL PROTECTED] wrote:
I couldn't find any other tests that run pbc_output_is() (but
admittedly, I didnt' look for too long), so it might be this function is
never used.
[parrot] 577 $ find t -name '*.t' | xargs grep -n pbc_ou
Leopold Toetsch wrote:
Am Samstag, 24. Februar 2007 17:05 schrieb Klaas-Jan Stol:
it seems the .pbc files are stored in the repository is that
desirable?
Yes for these files.
IMO, it would be enough to store the PIR only, and have that
compiled to PBC
If you have a
hi,
attached a patch for languages/Pynie, adding:
* more grammar rules
* statement.t for testing statements -- kinda simple, should be extended
* keyword rule, so that id's are not recognized as identifiers
regards,
kjs
Index: languages/pynie/src/parser/Grammar.pg
=
hi,
most languages that can run in interactive mode have some kind of
welcome message and prompt that is printed before the user can give any
input.
For example, Python prints:
Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit
(Intel)] on win
32
Type "help", "copyright", "cr
Patrick R. Michaud wrote:
On Sun, Feb 25, 2007 at 04:39:17PM +0100, Klaas-Jan Stol wrote:
most languages that can run in interactive mode have some kind of
welcome message and prompt that is printed before the user can give any
input.
Yes, this is helpful. But also one of the things
compiler object. Just call
$P0.'set_prompt'(0, ">>>")
$P0.'set_prompt'(1, "...")
(in case of Python/Pynie)
It should overwrite the prompt in that slot.
kjs
On Feb 25, 2007, at 11:24 AM, Klaas-Jan Stol wrote:
Patrick R. Michaud wrote:
On Sun,
hi,
I made some additional changes to PDD16:
* added an example to do a callback. I left in the "old" explanation,
but Im' not sure how much of that is still relevant.
* small text improvements wrt example nci
* removed "CHANGES" section: it was just duplicating the history
section. This PDD
chromatic wrote:
On Monday 26 February 2007 01:34, Klaas-Jan Stol wrote:
I made some additional changes to PDD16:
* added an example to do a callback. I left in the "old" explanation,
but Im' not sure how much of that is still relevant.
* small text improvements wrt exampl
hi,
I've done some more work on the grammar of Pynie.
This patch also includes the other patch I sent yesterday (so that one
can be skipped).
This grammar is ALMOST done, but now I'm kinda stuck, because there is
some infinite recursion :-(
It would also need some cleanup, and of course test
hi,
attached a patch that adds the last few bits of the Python grammar.
Please note that there may be bugs, but I put in all rules, (not using
the optable, that one is commented out)
I had to put some things into comments in the ASTgrammar, the expression
stuff needs work.
I removed the lef
hi,
attached is Grammar.pg for Pynie. It's complete, but it needs some
rework: the optable needs to be welded in again, instead of rec.decent
rules for parsing expressions. This mail is just for archiving purposes
(or in case someone feels brave). I'll have a look at putting back the
optable
jerry gay wrote:
On 2/26/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Sonntag, 25. Februar 2007 12:28 schrieb Klaas-Jan Stol:
> Can you tell whether pbc_output_is() can take PIR code and compile it
> during running the test? Or does is always expect the pbc file to be
> pr
hi,
attached my current version of languages/pynie's grammar.
I can't get the binary operators "is not" and "not in" working
correctly. The problem seems to be that "is parsed()" does not work.
When I specify a rule in the is parsed() annotation, and in the rule I
emit some message (just calli
hi,
attached an updated grammar for pynie/python. The PAST stuff is still
broken, have to work a bit on that.
THis grammar does part of the expression parsing recursive descent, and
from comparisons (==, != etc) to the power operator (**) through the
operator table.
regards,
kjs
## $Id: gra
hi,
I'm trying to compile parrot on cygwin, but it won't compile:
mpilers/imcc/parser_util.o compilers/imcc/pcc.o -lcrypt -lgmp -lreadline
compilers/imcc/main.c
/usr/bin/perl.exe tools/build/parrot_config_c.pl --mini > \
src/null_config.c
src/null_config.c
gcc -o miniparrot.exe compilers
[EMAIL PROTECTED] via RT wrote:
Hi,
Applied in 17281, thanks.
For your question, strdup is fine since these are not garbage
collectable strings (STRING*), just normal C char*'s. There is loads of
them used in IMCC. Unfortunately though, there is an issue in that we
don't free a load of 'em, or
On 3/5/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 3/5/07, Kevin Tew <[EMAIL PROTECTED]> wrote:
> Defining _CRT_SECURE_NO_DEPRECATE on the compiler command line is
> probably the right solution here.
> Kevin
>
i disagree. the reason C, C and C were
deprecated is because they're non-ansi. therefo
hi,
I've started a bit on a PIR tutorial on the wiki.
If anybody can spare a few moments, some feedback would be very welcome!
regards,
kjs
hi,
on
http://www.parrotcode.org/resources.html
there's a link named "glossary".
clicking on that link results in an empty page. The glossary is in
docs/glossary.pod
It should be put it in the website repository too.
regards,
kjs
hi,
In PIR, it's allowed to use ops as names for variables. For instance,
it's allowed to write:
.sub main
.local pmc inc
.end
However, when trying to increment your variable 'inc', you could write
.sub main
.local pmc inc
inc inc
.end
which not only looks strange, but will not even comp
James E Keenan wrote:
Klaas-Jan Stol wrote:
hi,
I've started a bit on a PIR tutorial on the wiki.
If anybody can spare a few moments, some feedback would be very welcome!
I am very glad to see this. One suggestion and one request for
clarification:
1. First bullet point in FAQ shou
Hi,
I'm working on parameters for Pynie. (functions are working! see my
latest patch, still pending)
I have some trouble with the tree transformation for Pynie. If anybody
knows how to solve this, help would greatly be appreciated.
The problem seems to be with PAST::VarList. Now, in Pynie thi
Nuno Carvalho via RT wrote:
Hi again,
On Tue Mar 13 16:17:56 2007, coke wrote:
Having a limit is more than reasonable, agreed: the goal of this
patch was to bring the code into agreement with the docs.
Consider this a poke to the Architect to verify/replace the previous
overturn of the
hi,
I noticed that some tests in languages/PIR are failing. I did not touch
the project for some time, and last time I worked on it, everything was
just fine.
Below some of the output I get. My guess it has something to do with the
test framework (wasn't that being refactored?)
Also, tests i
might make support for certain things easier. But a caveat of that is
handling something like '.Foo(")")' which requires an understanding of
PIR.
On Mar 21, 2007, at 4:53 PM, Klaas-Jan Stol (via RT) wrote:
# New Ticket Created by Klaas-Jan Stol
# Please include the
James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #42073]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42073 >
I expect that 'make realclean' will return my Parrot sand
James Keenan wrote:
On Mar 25, 2007, at 1:41 PM, Klaas-Jan Stol via RT wrote:
hi, I'm maintaining compilers/pirc. The pirc.in file (from which the
Makefile is generated) does contain:
realclean: clean
$(RM_RF) Makefile
$(RM_RF) pirc$(EXE)
When I type 'make realclean'
Klaas-Jan Stol wrote:
James Keenan wrote:
On Mar 25, 2007, at 1:41 PM, Klaas-Jan Stol via RT wrote:
hi, I'm maintaining compilers/pirc. The pirc.in file (from which the
Makefile is generated) does contain:
realclean: clean
$(RM_RF) Makefile
$(RM_RF) pirc$(EXE)
When I type
Hello,
I have a short and simple question w.r.t. syntax for constructing new
objects for the architect :-)
Currently, it's done through:
new P0, .Integer
or in PIR:
$P0 = new Integer # or .Integer
I thought to have read somewhere this will be changed into something
like this:
$P0 = Inte
hi,
Currently, compilers/pircdoes not have a test suite. I'd like to change
that, but am not sure how to handle this.
My idea was to have the PIR scripts parsed by pirc, which outputs
*exactly* the same source (on success), which then should be compiled by
IMCC.
I'm not sure how to achieve t
Hi,
As suggested by particle++, I added a vtable to the parser in
compilers/pirc.
Now, it's very easy to output PIR /or/ PAST :-) from the parser, without
too much extra code in the parser.
However, as I've only just begun, only very simple stuff will be output.
Changing the flag when creatin
"tuned dynamically", as in at run-time? alexandre mentioned this may
be possible on #parrot, but there may be trouble with decreasing the
generation count. i don't know if run-time tuning of the generation
count is necessary, but if so, i imagine that decreasing the count at
run-time could be ac
hi,
My question concerns functionality of PMCs and Objects.
while reading the docs about the functionality of classes and objects, I
read that the vtable entries of a class can be overridden to give the
class special behaviour. I'd like to know if I'm correct (I just
realized this), if I say
Leopold Toetsch wrote:
Klaas-Jan Stol wrote:
hi,
My question concerns functionality of PMCs and Objects.
while reading the docs about the functionality of classes and
objects, I read that the vtable entries of a class can be overridden
to give the class special behaviour. I'd li
1 - 100 of 375 matches
Mail list logo