Randy W. Sims wrote:
The test file below is pared down from Module::Build. The warning from
C comes up in several tests, not always causing test failures.
The same warning appears if you run MakeMaker as shown in the
Devel::Cover docs--it's not specific to Module::Build.
[EMAIL PROTECTED]:~/pro
Henrik Gulbrandsen wrote:
Hackers and Gentlemen - I bring you a preliminary Parrot Syntax Engine!
That's a really interesting stuff. I can imagine that it'll be really
useful for Parrot and that it could become more or less integrated.
Some unsorted questions and remarks:
- How fast is DParser co
Sam Ruby <[EMAIL PROTECTED]> wrote:
> See: http://xrl.us/emnk
=> dynclasses/pydic.pmc
> Except for fromkeys, get_string, and __new__, the logic is not Python
> specific, and could easily be refactored into a common base class for
> others to use.
Yep. The problem is that all current usage of ha
> the library 'libnci.so' is used for testing the Native Call Interface, not
> for implementing NCI. So the name 'libnci_test.so' make more sense.
>
> For Win32 I have moved 'libnci.def' for
> 'runtime/parrot/dynext/libnci_test.def'. However
> I could not test wether this works.
I've just noticed
Hi all,
I've been reading the internals list for a while more
or less regularly and as this is me first post, it is
about time, that I introduce myself:
My name is Sven Schubert, I am studying information
systems and business in Germany and currently I'm on
an exchange program (ERASMUS for fellow
On Fri, Jan 07, 2005 at 05:11:18PM +0100, Sven Schubert wrote:
> Hi all,
>
> I've been reading the internals list for a while more
> or less regularly and as this is me first post, it is
> about time, that I introduce myself:
>
> My name is Sven Schubert, I am studying information
> systems and b
On Thu, Jan 06, 2005 at 11:07:47PM +0100, Stéphane Payrard wrote:
: To get an huffmanized name and a clear one, I would like some support syntax:
:
: sub canon( $subjet as $s , $complement as $c ) {
: # code with lots of $s and $s
: }
Aliasing can currently be done with the binding oper
On Fri, Jan 07, 2005 at 10:28:32AM -0800, Larry Wall wrote:
> On Thu, Jan 06, 2005 at 11:07:47PM +0100, Stéphane Payrard wrote:
> : To get an huffmanized name and a clear one, I would like some support
> syntax:
> :
> : sub canon( $subjet as $s , $complement as $c ) {
> : # code with lots
StÃphane Payrard writes:
> > canon( subjet => $mysub, complement => $mycomp );
> > canon( :subjet($mysub) :complement($mycomp) );
>
> I suppose you meant
>
> canon( :subjet($mysub), :complement($mycomp) );
The comma is optional between those kinds of pairs.
> btw, are the parenthes
Stéphane Payrard skribis 2005-01-07 21:23 (+0100):
> > my $s := $subjet;
> > my $c := $complement;
> That's what I wanted to avoid.
Why? Do you expect to use lots of one letter aliases?
I think it's one of the most effective ways to kill readability.
Juerd
Luke Palmer wrote:
Well, it'll still get that bad rap because it's as syntactically
flexible as ever (moreso even), so people have all the freedom they want
to write code ugly as sin.
Anyway, if you want to see more Perl 6 syntax, why don't you post some
"how do I"s to the list, and I'll reply with
On Fri, 2005-01-07 at 11:10, Leopold Toetsch wrote:
> - How fast is DParser compared to bison/flex?
> - What about memory usage compared to bison/flex?
I will leave those questions for John, but a first guess would be that
they are a bit too general to be meaningful. One would expect DParser to
be
James E Keenan wrote:
Randy W. Sims wrote:
The test file below is pared down from Module::Build. The warning from
C comes up in several tests, not always causing test
failures. The same warning appears if you run MakeMaker as shown in
the Devel::Cover docs--it's not specific to Module::Build.
[
13 matches
Mail list logo
