Author: larry
Date: Fri Oct 26 02:53:13 2007
New Revision: 14467
Modified:
doc/trunk/design/syn/S03.pod
Log:
String composition operators now get their own two precedence levels looser
than number composers but tighter than junctions, as suggested by tye++.
Modified:
chromatic wrote on Sat, Aug 25, 2007 at 11:09:24PM PDT:
There's almost no vtable entry documentation in src/pmc/undef.pmc. You can
copy it almost verbatim from almost any other PMC. This is an easy task that
requires almost no C or Perl knowledge.
This isn't much documentation, and I hope
New test files contributed in r22500 and r22501.
The conversion of Lua is ended.
The main issue was with the grammar parser :
Lua keywords were recognized as identifier.
I solve it by renaming the rule 'name' to 'Name' (r22499).
This rule is defined in lua/src/lua51.pir and used by lua/src/lua51.pg
So, that sounds strange.
François.
# New Ticket Created by Will Coleda
# Please include the string: [perl #46933]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46933
Currently, Data::Dumper treats Undef pmcs like any other pmcs. When dumping,
then,
I just remembered you wrote the 'name' rule and keyword handling yourself by
hand. I guess the solution below doesn't help you much then. Is there any
reason not to replace the handwritten stuff by the more standard (and
maintainable?) PGE version of name/keyword handling?
kjs
On 10/26/07,
I think it can be solved by adding a precondition the identifier rule,
for instance, like so:
rule identifier {
!keyword [a-zA-Z]*
}
(an identifier is a series of letters, but it's not in keyword; not sure
if the ! ... syntax is still valid, or that it was changed recently).
rule keyword {
Author: particle
Date: Fri Oct 26 10:26:57 2007
New Revision: 22505
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
[PDD23]: typo and formatting fixes
Modified: trunk/docs/pdds/pdd23_exceptions.pod
==
---
On Oct 25, 2007, at 4:35 PM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46927]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46927
The attached patch
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46937]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46937
This patch enables the t/codingstd/c_parens.t coding standard to pass
completely.
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46939]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46939
The attached patch adds dependencies to lib/Parrot/Pmc2c/PCCMETHOD.pm
if the .pmc
On Friday 26 October 2007 15:03:12 Paul Cochrane wrote:
The attached patch adds dependencies to lib/Parrot/Pmc2c/PCCMETHOD.pm
if the .pmc uses PCCMETHODs. This should also then allow the
t/codingstd/pccmethod_deps.t test to pass.
+1
-- c
On 27/10/2007, chromatic [EMAIL PROTECTED] wrote:
On Friday 26 October 2007 15:03:12 Paul Cochrane wrote:
The attached patch adds dependencies to lib/Parrot/Pmc2c/PCCMETHOD.pm
if the .pmc uses PCCMETHODs. This should also then allow the
t/codingstd/pccmethod_deps.t test to pass.
+1
With modification of one test file in r22511, we have achieved 100% test
coverage of this package's code. Resolving ticket.
Author: larry
Date: Fri Oct 26 16:54:25 2007
New Revision: 14468
Modified:
doc/trunk/design/syn/S06.pod
doc/trunk/design/syn/S12.pod
Log:
Some clarifications suggested by Wolfgang Laun++ and TheDamian++ and others++
Modified: doc/trunk/design/syn/S06.pod
Addition of two more test files in r22513 enabled us to eke out a bit
more test coverage, getting us to 100% across the board.
Two test files contributed in r22514 bring us to 100% test coverage on
this configuration step class. Resolving ticket.
On Fri Jun 08 06:53:46 2007, ptc wrote:
In the file config/inter/pmc.pm, there is the comment:
# XXX:leo do we really need an interactive step for this
# user could deactivate vital PMCs like SArray
# so there would be tests needed, that check for vital classes
This relates to
18 matches
Mail list logo
