On Tue, Aug 26, 2008 at 11:00 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> jerry gay wrote:
>>>
>>> #+ and #- is lisp so I don't want to destroy #+ the syntax rules.
>>> #IF(): is quite short and easy to read.
>>>
>> i know it was all caps before, but do we need to continue that trend?
>> i find
jerry gay wrote:
#+ and #- is lisp so I don't want to destroy #+ the syntax rules.
#IF(): is quite short and easy to read.
i know it was all caps before, but do we need to continue that trend?
i find it ugly.
All-caps is the Parrot coding standard for macros and #defines, and
these fall in
On Tue, Aug 26, 2008 at 2:34 AM, Reini Urban <[EMAIL PROTECTED]> wrote:
> I'll go now for something like
>
> #IF(key1|key2&(key3&!key4))
> #IFNOT(key1|key2&(key3&!key4))
>
> And probably a shortcut for the negative else clause, like
> #IF(cygwin):
> #ELSE:
>
> #+ and #- is lisp so I don't want to d
2008/8/26 Allison Randal <[EMAIL PROTECTED]>:
>> On Mon, 25 Aug 2008, Reini Urban wrote:
>>>
>>> To clarify my bold statement:
>>> The ALGOL-like syntax is not "sane" because,
>>> * it is hard to parse,
>
> Not actually true. It's just different to parse. And, in general Parrot
> optimizes for maki
On Mon, 25 Aug 2008, Reini Urban wrote:
To clarify my bold statement:
The ALGOL-like syntax is not "sane" because,
* it is hard to parse,
Not actually true. It's just different to parse. And, in general Parrot
optimizes for making code easy to *read* even if it is slightly harder
to parse. We
On Mon, 25 Aug 2008, Reini Urban wrote:
> Reini Urban schrieb:
> > 2008/8/24 Allison Randal <[EMAIL PROTECTED]>:
> > > Reini Urban wrote:
> To clarify my bold statement:
> The ALGOL-like syntax is not "sane" because,
> * it is hard to parse,
> * it forbids our keywords AND, NOT and OR as config_h
Reini Urban wrote:
> Moritz Lenz schrieb:
>> Reini Urban wrote:
>>> Moritz Lenz schrieb:
Reini Urban wrote:
> Attached are updates to the cygwin070patches branch.
> Thanks for applying the patches!
applied as r30543.
>>> And this one also please.
>>>
>>> fix cuddled else and some
Moritz Lenz schrieb:
Reini Urban wrote:
Moritz Lenz schrieb:
Reini Urban wrote:
Attached are updates to the cygwin070patches branch.
Thanks for applying the patches!
applied as r30543.
And this one also please.
fix cuddled else and some beautification.
Also applied (r30547).
And one mor
Reini Urban wrote:
In lib/Parrot/Configure/Compiler.pm, I agree that 'CONDITIONED_LINE' and
'INVERSE_CONDITIONED_LINE' aren't the clearest names, but '+' and '-' are
far less clear. Change them to something meaningful like 'SHOW_LINE_IF' and
'HIDE_LINE_IF'. We can note the change in DEPRECATED.
Reini Urban wrote:
> Moritz Lenz schrieb:
>> Reini Urban wrote:
>>> Attached are updates to the cygwin070patches branch.
>>> Thanks for applying the patches!
>>
>> applied as r30543.
>
> And this one also please.
>
> fix cuddled else and some beautification.
Also applied (r30547).
Moritz Lenz schrieb:
Reini Urban wrote:
Attached are updates to the cygwin070patches branch.
Thanks for applying the patches!
applied as r30543.
And this one also please.
fix cuddled else and some beautification.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
Index: src/library.c
=
Reini Urban wrote:
> Attached are updates to the cygwin070patches branch.
> Thanks for applying the patches!
applied as r30543.
Moritz
--
Moritz Lenz
http://moritz.faui2k3.org/ | http://perl-6.de/
Attached are updates to the cygwin070patches branch.
Forget it. The Data.pm errors were still in.
This is better.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
cygwin070patches_3.patch.gz
Description: GNU Zip compressed data
Reini Urban schrieb:
2008/8/24 Allison Randal <[EMAIL PROTECTED]>:
Reini Urban wrote:
You want one patch only against HEAD? That's easy.
But I dislike the idea, as it violates the usage of single tickets.
This is different than the usual case as it's a collection of dependent
patches that can'
2008/8/24 Allison Randal <[EMAIL PROTECTED]>:
> Reini Urban wrote:
>>
>> You want one patch only against HEAD? That's easy.
>> But I dislike the idea, as it violates the usage of single tickets.
>
> This is different than the usual case as it's a collection of dependent
> patches that can't be eval
Reini Urban wrote:
You want one patch only against HEAD? That's easy.
But I dislike the idea, as it violates the usage of single tickets.
This is different than the usual case as it's a collection of dependent
patches that can't be evaluated independently. Splitting them out is
actually more
Allison Randal schrieb:
Reini Urban wrote:
Moritz Lenz schrieb:
Against which svn revision should I apply those patches for testing?
I'll try to be uptodate against HEAD with the patches in my SVN repo.
But things are changing fast over there.
config/gen/makefiles/root.in was changed by th
Reini Urban wrote:
Moritz Lenz schrieb:
Against which svn revision should I apply those patches for testing?
I'll try to be uptodate against HEAD with the patches in my SVN repo.
But things are changing fast over there.
config/gen/makefiles/root.in was changed by the ncigen merge yesterday.
Moritz Lenz schrieb:
Reini Urban wrote:
> See
http://code.google.com/p/cygwin-rurban/source/browse/#svn/trunk/release/parrot/patches
http://code.google.com/p/cygwin-rurban/source/browse/trunk/release/parrot/patches/series
defines the order.
I tried to apply those patches stupidly both agains
Reini Urban wrote:
> See
> http://code.google.com/p/cygwin-rurban/source/browse/#svn/trunk/release/parrot/patches
>
> http://code.google.com/p/cygwin-rurban/source/browse/trunk/release/parrot/patches/series
> defines the order.
I tried to apply those patches stupidly both against HEAD and agains
2008/8/22 Allison Randal <[EMAIL PROTECTED]>:
>> As my number of patches is too big, and the size is too big,
>> I update them only in my public SVN repo, not in the tickets anymore.
>> And the order in which they should be applied is important.
>>
>> See
>> http://code.google.com/p/cygwin-rurban/
Reini Urban wrote:
As my number of patches is too big, and the size is too big,
I update them only in my public SVN repo, not in the tickets anymore.
And the order in which they should be applied is important.
See
http://code.google.com/p/cygwin-rurban/source/browse/#svn/trunk/release/parrot/pa
2008/8/17 Reini Urban <[EMAIL PROTECTED]>:
> FYI:
> The cygwin release for parrot-0.7.0-1 will contain the following yet
> unapplied patches to make it work:
>
> (in this order from my quilt series file)
> 39742-installed-conflict.patch
> 56544-install_files.patch
> 57006-opengl-cyg.patch -p0
I've
23 matches
Mail list logo
