On Wed, Jul 30, 2008 at 8:22 PM, Will Coleda via RT <
[EMAIL PROTECTED]> wrote:
> On Wed, Jul 30, 2008 at 9:13 AM, via RT Klaas-Jan Stol
> <[EMAIL PROTECTED]> wrote:
> > # New Ticket Created by Klaas-Jan Stol
> > # Please include the string: [perl #57410]
> >
On Wed, Jul 30, 2008 at 9:06 PM, via RT Will Coleda <
[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #57438]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=57438 >
>
>
Implemented in r29908.
kjs
On Wed, Jul 30, 2008 at 7:51 PM, via RT Will Coleda <
[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #57430]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket
Attached is a patch that does this, but I'm not quite sure about the last 2
statements.
Hence, this is submitted as a patch instead of me applying it myself.
kjs
On Wed, Jul 30, 2008 at 7:47 PM, via RT Will Coleda <
[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Will Coleda
> # Please inc
R. Michaud <[EMAIL PROTECTED]>wrote:
> On Thu, Jul 31, 2008 at 10:07:49AM +0100, Klaas-Jan Stol wrote:
> > On Wed, Jul 30, 2008 at 9:06 PM, via RT Will Coleda wrote
> > > From PDD19:
> > >
> > > =item .pragma n_operators [deprecated]
> >
> > does thi
On Wed, Aug 6, 2008 at 8:30 PM, Jonathan Worthington <[EMAIL PROTECTED]>wrote:
> Will Coleda wrote:
>
>> Can you describe a situation where this occurs that isn't a bug in the
>> register allocator?
>>
>>
> Yes. IIRC, it was added when I was working on the .Net bytecode translator,
> and it needed
[this message was not sent to list, which it seems it should have; hence the
forward.]
-- Forwarded message --
From: Andrew Whitworth via RT <[EMAIL PROTECTED]>
Date: Thu, Aug 7, 2008 at 12:11 AM
Subject: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".."
(or somet
On Thu, Aug 7, 2008 at 12:45 PM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 6, 2008 at 3:30 PM, Jonathan Worthington <[EMAIL PROTECTED]>
> wrote:
> > Will Coleda wrote:
> >>
> >> Can you describe a situation where this occurs that isn't a bug in the
> >> register allocator?
> >>
> >
> >
On Thu, Aug 7, 2008 at 1:33 PM, Jonathan Worthington <[EMAIL PROTECTED]>wrote:
> Will Coleda wrote:
>
>> So, again, do we in parrot want to support the ability to dig into our
>> callers register set and pull out a particular register since we have
>> no way to say which register that is when we'r
On Fri, Aug 8, 2008 at 12:57 PM, Patrick R. Michaud <[EMAIL PROTECTED]>wrote:
> On Thu, Aug 07, 2008 at 10:15:24AM -0400, Will Coleda wrote:
> > Now, if the problem is that the register allocator is broken, then
> > let's fix the register allocator. If :unique_reg is just a workaround
> > because
What's the general feeling about this proposal?
Any thoughts of the architect?
kjs
On Tue, Aug 5, 2008 at 6:47 PM, via RT Klaas-Jan Stol <
[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Klaas-Jan Stol
> # Please include the string: [perl #57634]
> # in the subjec
What's the general feeling about this proposal?
Any thoughts of the architect?
thanks,
kjs
On Thu, Aug 7, 2008 at 5:17 PM, Bob Rogers <[EMAIL PROTECTED]>wrote:
> From: "Andrew Whitworth" <[EMAIL PROTECTED]>
> Date: Thu, 7 Aug 2008 11:36:16 -0400
>
> On Thu, Aug 7, 2008 at 11:18 AM, Bob Rog
On Sat, Aug 16, 2008 at 9:41 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>> On Wed Aug 06 05:53:07 2008, kjs wrote:
>>
>>> My proposal would be to change the concatenate dot into "..", which looks
>>> lik
On Mon, Aug 18, 2008 at 10:31 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>>
>> On Sat, Aug 16, 2008 at 9:41 AM, Allison Randal <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:
>>
>>Klaas-Jan Stol wrote:
docs/imcc/macros.pod was integrated into pdd19 some time ago. That's all
information available on macros, currently
kjs
On Mon, Aug 25, 2008 at 10:08 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
> pdd19_pir.pod references the not-existing docs/imcc/macros.pod.
>
> It would be nice if this document
On Thu, Aug 28, 2008 at 10:07 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
>> Opcode names are not reserved words in PIR, and may be used as variable
>> names.
>> For example, you can define a local variable named C. [See RT
>> #24251]
>> +Note that by using an opc
On Fri, Aug 29, 2008 at 11:06 AM, Klaas-Jan Stol <[EMAIL PROTECTED]>wrote:
>
>
> On Thu, Aug 28, 2008 at 10:07 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
>
>> [EMAIL PROTECTED] wrote:
>>
>>> Opcode names are not reserved words in PIR, and may be
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol (via RT) wrote:
>
>>
>> The parentheses surrounding the arguments are mandatory. Besides making
>> sequence break more conspicuous, this is necessary to distinguish this
>
On Sat, Aug 30, 2008 at 12:27 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>>>>> This is another one of those muddy cases in PIR where words conflict
>>>> when
>>>> they shouldn't. I can't think of a
On Tue, Sep 2, 2008 at 12:43 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>> This must make the following syntax rule illegal:
>>
>> target = null
>>
>> because if "null" is declared as a .local, you can&#x
On Tue, Sep 2, 2008 at 2:28 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>> So, preferably, the special words in PIR will be allowed as identifiers
>> ('if','unless', 'null') and PIR will DWIM. What abo
I checked in some major changes that allow all keywords (types and if, null,
etc.) as identifiers. Cleanup and maybe a refactor will follow later.
kjs
On Wed, Sep 3, 2008 at 10:35 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>> On Tue, Sep 2, 2008 a
On Tue, Sep 2, 2008 at 8:08 AM, François Perrad <[EMAIL PROTECTED]>wrote:
> It seems that PIR uses only one name space of identifiers.
>
> $ cat const.pir
> .const int cst = 42
>
> .sub 'cst'
>print cst
> .end
>
> $ parrot const.pir
> error:imcc:undefined identifier 'cst'
>
>in file 'c
On Tue, Sep 2, 2008 at 12:43 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>>
>> This must make the following syntax rule illegal:
>>
>> target = null
>>
>> because if "null" is declared as a .local, you can&#x
On Fri, Sep 5, 2008 at 1:28 PM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 5, 2008 at 3:45 AM, Christoph Otto via RT
> <[EMAIL PROTECTED]> wrote:
> > On Fri Jun 27 13:14:53 2008, coke wrote:
> >>
> >> While I think this particular example is now valid with the new calling
> >> convention
It seems that the error condition refers to the case where too many
arguments are passed (#args > #params).It's not really "overflow" in that
sense, IMHO, just "too many arguments passed".
I think an exception is already thrown when that happens, not sure.
kjs
On Tue, Sep 9, 2008 at 12:02 AM, c
hi,
recently I had a good look at Parrot's Makefile to figure out what link
flags I need to link PIRC against libparrot.
This worked out quite well, and I'm now able to link in libparrot so PIRC
can now call all Parrot functions.
(the only major thing that needs to be done to get rid of IMCC is gen
sorry, documentation and source should be reorganized at some point. For
now, please check out compilers/pirc/README.pod.
sorry for the confusion,
kjs
On Tue, Sep 9, 2008 at 5:31 PM, NotFound <[EMAIL PROTECTED]> wrote:
> > I put the commands that I'm using in the README file (but that's for MSVC
On Sat, Aug 30, 2008 at 10:40 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
>
>> On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>>> Yes, it will be deprecated, or a
On Fri, Oct 3, 2008 at 2:23 PM, I Sop <[EMAIL PROTECTED]> wrote:
> > From: Patrick R. Michaud via RT <[EMAIL PROTECTED]>
> > Subject: Re: [perl #59576] [PATCH] 'property' scope for PAST::Var
> > To: [EMAIL PROTECTED]
> > Date: Friday, October 3, 2008, 12:31 PM
> > On Thu, Oct 02, 2008 at 02:16:01P
On Mon, Oct 13, 2008 at 2:10 AM, Andrew Whitworth <[EMAIL PROTECTED]>wrote:
> On Sun, Oct 12, 2008 at 9:27 AM, via RT Klaas-Jan Stol
> <[EMAIL PROTECTED]> wrote:
> > currently, the .line directive takes both an integer (for line number)
> and a
> > string (for fil
On Mon, Oct 20, 2008 at 6:18 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Sunday 19 October 2008 14:02:58 Klaas-Jan Stol wrote:
>
> > when running code as this:
> > .sub main :immediate
> > load_bytecode "foo.pir"
> > .end
> >
> > (a
I'd say kill it, and if we ever want to introduce new pragmas into PIR, we
reintroduce. This way, .pragma keyword is not recognized without a reason.
(recently I've become a great fan of being able to override commandline
options with directives in the file processed; .pragma directive would be
goo
On Sat, Nov 8, 2008 at 9:22 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Wednesday 05 November 2008 14:31:21 [EMAIL PROTECTED] wrote:
>
> > Modified:
> >trunk/compilers/pirc/new/pir.l
> >trunk/compilers/pirc/new/pirlexer.c
> >trunk/compilers/pirc/new/pirlexer.h
> >
> > Log:
> > [pirc]
I'm not entirely sure whether it was *just* a rename... ISTR there was also
something to do with a look-up of names. Pm knows more about it :-)
(admittedly, the topic is not well-defined then.)
kjs
On Thu, Nov 20, 2008 at 4:21 PM, Will Coleda via RT <
[EMAIL PROTECTED]> wrote:
> On Sun Nov 16 11:
On Sun, Nov 23, 2008 at 10:08 PM, Jonathan Worthington
<[EMAIL PROTECTED]>wrote:
> Klaas-Jan Stol via RT wrote:
>
>> On Thu Dec 13 04:35:13 2007, pmichaud wrote:
>>
>>
>>> On Sat Sep 29 08:57:28 2007, kjs wrote:
>>>
>>>
>>>> A
On Mon, Nov 24, 2008 at 2:00 AM, Patrick R. Michaud <[EMAIL PROTECTED]>wrote:
> On Mon, Nov 24, 2008 at 02:31:58AM +0100, Jonathan Worthington wrote:
> > Oh, argh, so .line now carries the file *and* the line number?.I wanted
> > it to just carry the line number (the clue's in the name... ;-)) and
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
1 - 100 of 377 matches
Mail list logo
