# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39329]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39329 >
PMC_str_val and family aren't guaranteed to work for subclasses, so
they should be
We are looking at introducing continuous builds/smoke tests at
work across a number of platforms (mainly Windows and Unix),
building a number of different languages (mainly C++).
I quick google uncovered the list below.
Anyone got any advice?
Thanks,
/-\
Perl
* AutoBuild: http://www.auto
Author: larry
Date: Wed Jun 7 18:51:18 2006
New Revision: 9529
Modified:
doc/trunk/design/syn/S04.pod
Log:
Semantics of bare block clarified.
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.po
Just an update:
I've started coding (in haskell, to be used with Pugs). I've got file input,
I've got a data structure for the AST, now I just have to make them play
nicely together. I'll start implementing translations soon, so any other
corrections would be appreciated.
Thanks to everyone who'
Author: larry
Date: Wed Jun 7 08:55:55 2006
New Revision: 9528
Modified:
doc/trunk/design/syn/S03.pod
Log:
putter++ notes that prec table is missing .<>
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design
Author: audreyt
Date: Wed Jun 7 08:30:53 2006
New Revision: 9527
Modified:
doc/trunk/design/syn/S06.pod
Log:
* S06: Fixed a minor typo noticed by szbalint++.
Modified: doc/trunk/design/syn/S06.pod
==
--- doc/trunk/de
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
* Thomas Wittek <[EMAIL PROTECTED]> [2006-06-07 15:05]:
> I guess that the architecture/design for such a flexible piece
> of software will be relatively complex.
All I can think of is “YAGNI”.
Defining a syntax in a configuration file doesn’t strike me as a
particularly smart move. You will eith
Damn, forgot the link.
Thomas Wittek schrieb:
> That's mainly what I did as stated in my first post[1]. [...]
[1]:
news://nntp.perl.org:119/[EMAIL PROTECTED]
Juerd schrieb:
> * Markdown does not have tables.
> * Textile does not have paragraphs in table cells.
> * Kwiki does not have paragraphs in table cells.
>
> Unless someone comes up with another way to do side-by-side layouts
> (extremely useful for showcasing differences between Perl 5 and Perl 6
Udo Güngerich schrieb:
> Thomas Wittek wrote:
>> Unfortunately you probably have to throw away/heavily modify earlier
>> increments, if you add features like a flexible syntax, which will need
>> a different internal infrastructure.
>
> Well, if object-oriented design has any advantage at all, her
Hi,
I have never understand this "my wiki syntax is better than yours"
thing. It's like "my templateing engine is better than yours".
I feel like which should have "wiki.conf" with :
...
syntaxhandler = SuperbPerl6Wiki::Syntax::MediaKwikiMikiBiky
...
That shall please everyone. :)
- Fagzal
Sage La Torra writes:
> "interpolative context" ment the perl 5 side, where the double quotes
> should cause interpolation.
Yes, but not for entire hashes; the percent character isn't special in
Perl 5 double-quoted strings, as Aaron said:
> On 6/6/06, Aaron Crane <[EMAIL PROTECTED]> wrote:
>
>
13 matches
Mail list logo