> Icelandic: laukur (Incidentally, none of you will ever guess how to
> correctly pronounce that.)
Russian: luk (pronounced similar to English "look"). For some reason,
Icelandic translation of onion is much closer to Russian than any other
variants...
Thu May 26 22:49:09 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
* Make Pugs.AST.Internals compilation more bearable
Thu May 26 22:52:31 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
* Make Pugs.Parser compilation more bearable
New patches:
[Make Pugs.AST.Internals compilation more bearable
S
# New Ticket Created by François PERRAD
# Please include the string: [perl #35997]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35997 >
This patch allows configuration of gdbm with MinGW32.
Francois Perrad
gdbm.patch
# New Ticket Created by Dino Morelli
# Please include the string: [perl #35994]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35994 >
Added tests in t/p6rules/capture.t for named alias captures.
file:
t/p6rules/capture
You get all those possibilities whenever you install any new version of
a module you get from someone else, regardless of a p5->p6 hop. In p6,
when you say "use Digest;", you are specifically asking for what p6
considers the "latest" version. In p5, it was "first match on libpath".
Except that
On Thu, 26 May 2005, Patrick R. Michaud wrote:
The continuing exchanges regarding junctions, and the ongoing tendency
by newcomers to think of them and try to use them as sets, makes
me feel that it might be worthwhile to define and publish a standard
C class and operations sooner rather than la
Adam Kennedy wrote:
You get all those possibilities whenever you install any new version
of a module you get from someone else, regardless of a p5->p6 hop. In
p6, when you say "use Digest;", you are specifically asking for what
p6 considers the "latest" version. In p5, it was "first match on
Kevin Tew <[EMAIL PROTECTED]> wrote:
> Adds tests and fixes incorrect implementation.
Thanks, applied - 8173
leo
Bob Rogers <[EMAIL PROTECTED]> wrote:
> This patch adds deletion to the same case. Testing also caught a
> missing label in the original version, for a branch that was never
> taken.
Thanks, applied - 8175
leo
Roger Browne <[EMAIL PROTECTED]> wrote:
> This pasm fragment...
> index I1, "u", "t", -123456
> print I1
> print "\n"
> end
> ...prints -32 instead of the expected -1.
... or somethin else, start wasn't verfied properly.
Fixed (r8176), thanks for testing.
leo
François PERRAD <[EMAIL PROTECTED]> wrote:
> a new version of this patch.
Thanks, applied - 8174
leo
In Synopsis 13 MMD is discussed as the mechanism for overloading an
operator.
Many a times I would like to overload a method of a class.
I just played around with this:
http://svn.openfoundry.org/pugs/modules/Class-Events/lib/Class/Events.pm
Notice how the Named event variation appends
François" PERRAD <[EMAIL PROTECTED]> wrote:
> This patch allows configuration of gdbm with MinGW32.
Thanks, applied - 8177
leo
# New Ticket Created by Roger Browne
# Please include the string: [perl #36003]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36003 >
The following pir program:
.sub test @MAIN
$I1 = mod 3, 3
print "3 mod 3 = "
On Thu, May 26, 2005 at 10:58:12PM -0400, Samuel Bronson wrote:
> Thu May 26 22:49:09 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
> * Make Pugs.AST.Internals compilation more bearable
>
> Thu May 26 22:52:31 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
> * Make Pugs.Parser compilation more be
Roger Browne (via RT) wrote:
The following pir program:
[ ... ]
...but I believe it should print this:
3 mod 3 = 0
-3 mod 3 = 0
3 mod -3 = 0
-3 mod -3 = 0
IMHO too. I've updated intval_mod to consider the case of zero reminder
with negative args (rev 8178).
Thanks for testing,
leo
Markus Laire wrote:
@m[0;1] is a multidim deref, referencing the 4.
Referencing the 2, I hope?
Doh!
Yes, the 2.
Really?
I consider this puzzling indicative that the (,) vs. [,] distinction
in Perl6 falls into the same category as e.g. starting the capture
variables at $1.
@m here has _sin
Juerd wrote:
From S02: "Array and hash variable names in scalar context
automatically produce references."
Since [...] produces a scalar arrayref, we end up with an arrayref one
both sides of the =.
No.
There is no scalar context on the LHS of the assignment operator.
And, assigning to a re
I would love to see a document (one per editor) that describes the
Unicode characters in use and how to make them. The Set implementation
in Pugs uses (at last count) 20 different Unicode characters as
operators.
While I'm sure these documents exist on the web somewhere, since P6 is
the first time
Juerd wrote:
And, assigning to a reference is impossible, as a reference is a VALUE,
not a VARIABLE (container).
What should hinder &infix:{'='}:(Ref, Int: --> Int) to exist and be
usefull at least if the Ref is known to something that derefs it
and then finds the new referee? On the Perl6 lang
"TSa (Thomas Sandlaß)" skribis 2005-05-27 16:22 (+0200):
> This argumentation breaks down as soon as you regard &infix:{'='} as
> an operator like many others.
Which we don't, making this discussion much easier for everyone.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolutio
"TSa (Thomas Sandlaß)" skribis 2005-05-27 15:44 (+0200):
> Could the ones who know it, enlighten me *why* it has to be so?
> What does it buy the newbie, average, expert Perl6 programmer?
> The answer "that's how Perl5 did it" is a good default, but
> never hindered @Larry to change things.
Becaus
Parrot's capabalities are increasing steadily, programs written for
Parrot especially those emitted from compilers are getting bigger and
bigger.
Debugging Parrot programs didn't keep up with the pace and is becoming a
PITA.
Some notes.
*) tracing or debugging an interpreter shall not influen
Leopold Toetsch wrote:
[2] see USE_TRACE_DEBUG in src/runops_cores.c
USE_TRACE_INTERP
sorry,
leo
Hi,
# Way 1
my $MEANING_OF_LIFE is constant = 42;
# Way 2
my &MEANING_OF_LIVE = -> () { 42 };
# or
sub MEANING_OF_LIVE () { 42 }
# Then one can use sigilless constants:
say MEANING_OF_LIVE;
# Way 3 (still possible?)
use constant MEANING_OF_LIVE => 42;
# Way 4 (evil?)
Ingo Blechschmidt wrote:
# Please add more ways :)
enum ;
my &MEANING_OF_LIVE = 42; # But might be considered evil sigilless mode
--
TSa (Thomas Sandlaß)
On 5/26/05, Adrian Howard <[EMAIL PROTECTED]> wrote:
> -No class invariants?
Soon!
> -You do mention that tweaking @_ in the pre/post blocks will
> affect the @_ passed to the method. You don't say that having pre/
> posts that have side effects is evil. You probably should :-)
Reflecti
HaloO Juerd,
you wrote:
Because the alternative is to drop context.
...
Then we lose the point for having different sigils, and everything gets
a dollar sign.
Isn't the strong type system adequate compensation?
Especially when the sigils denote the level below
which you can't go in untypedness
Hi,
"TSa (Thomas Sandlaß)" wrote:
> my &MEANING_OF_LIVE = 42; # But might be considered evil sigilless
> mode
is that allowed (as 42 is a Num (or an Int), not a Code)?
Do (most of) the basic types morph themselves into Codes, when needed?
say 42();# 42?
say "Perl"();
Ingo Blechschmidt wrote:
is that allowed (as 42 is a Num (or an Int), not a Code)?
I don't know, but guess not.
Do (most of) the basic types morph themselves into Codes, when needed?
I don't consider it type morphing. If your examples parse
at all they will be dispatched as usual
say 4
Will Coleda <[EMAIL PROTECTED]> wrote:
> The attached patch provides a (possibly naive) implementation of the
> remaining escape characters from:
>
> http://www.tcl.tk/man/tcl8.5/TclCmd/Tcl.htm#M16
>
> that were missing, namely
>
> \ooo (octal)
>
> \xhh (hex)
>
> and
>
> \u (unicode)
>
On Fri, May 27, 2005 at 10:29:39AM -0400, Rob Kinyon wrote:
> I would love to see a document (one per editor) that describes the
> Unicode characters in use and how to make them. The Set implementation
> in Pugs uses (at last count) 20 different Unicode characters as
> operators.
Good idea. A mode
Hi,
"TSa (Thomas Sandlaß)" wrote:
> Ingo Blechschmidt wrote:
>> Or did you simply forget the braces around 42? :)
>
> No, it was intented for seeing what the reactions will be :)
:)
> Just using &foo as unsigiled variable. This might need
>
> my &foo is rw;
I don't think this will DWYW, as fi
Jim,
"test" in what sense? Is this supposed to be a module like Test::More
or Test::Deep which builds on Test::Builder and which will ultimately
generate an 'ok'? If so, what does the interface for that look like?
It'll look like this: (in a Test::Unit::TestCase subclass)
my $fh =C
Luke Palmer wrote:
So I suppose that's my proposal. Allow, even encourage, overloading
of =:=, but only for value types. I've been thinking that we ought to
provide a standard role for making something a value type. Maybe it
would require definition of =:=.
I would like to propose something
--- Ian Langworth <[EMAIL PROTECTED]> wrote:
> Reflecting upon this, I'm not even sure why I'd want argument
> modification as a feature. (Maybe I still had Hook::LexWrap on the
> brain.) I might just take this out.
I vote for taking it out. I view contracts to be similar to exceptions
in one res
On 5/27/05, Ovid <[EMAIL PROTECTED]> wrote:
> > Class::Agreement's contracts should be
> > nearly as light as putting "die unless" in your methods.
>
> What? I had no idea. Was that in the docs and I overlooked it? To
> me, this is probably one of the strongest features of Class::Agreement
> a
Vsevolod (Simon) Ilyushchenko wrote:
> Hi,
>
> I'd like to suggest a module that I came up with to test CGI file
> uploading logic. I have not found anything else like it.
have you seen Apache-Test yet?
http://search.cpan.org/dist/Apache-Test/
I find it hard to understand modules like this a
On 27 May 2005, at 16:21, Ian Langworth wrote:
[snip]
When you say "automatic," I think of source filtering. Do you simply
mean an alias for the first argument? If so, I think it's best to
leave that up to the programmer. You can always use shift.
Fair enough. I just hate having the duplicatio
Fri May 27 14:04:13 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
* Add export list to Pugs.Types
New patches:
[Add export list to Pugs.Types
Samuel Bronson <[EMAIL PROTECTED]>**20050527180413] {
hunk ./src/Pugs/Types.hs 13
-module Pugs.Types where
+module Pugs.Types (
+Type(..), mkType, any
When we heard that Larry didn't acutally want $$foo to infinitely
dereference, some of us were overjoyed, and others severely
disappointed. Both transparent dereferencing (infinite $$foo) and
opaque dereferencing (one-level $$foo) have their uses, but they are
definitely distinct. Instead of addi
Hi,
what is the default invocant of methods?
method blarb ($normal_param) {...}
# Same as
method blarb (Class | ::?CLASS $invocant: $normal_param) {...}
# or
method blarb (::?CLASS $invocant: $normal_param) {...}
# ?
I prefer the latter, as then one can't accidentally call a instance
On 27 May 2005, at 18:25, Ovid wrote:
--- Ian Langworth <[EMAIL PROTECTED]> wrote:
Reflecting upon this, I'm not even sure why I'd want argument
modification as a feature. (Maybe I still had Hook::LexWrap on the
brain.) I might just take this out.
I vote for taking it out. I view contract
On Fri, May 27, 2005 at 02:05:46PM -0400, Samuel Bronson wrote:
> Fri May 27 14:04:13 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
> * Add export list to Pugs.Types
Thanks, applied -- I've sent an invitation for you to become a
committer, too. Welcome aboard!
/Autrijus/
pgpWkQV3jHQmd.pgp
Des
Luke Palmer skribis 2005-05-27 20:59 (+):
> Opaque references always need to be explicitly dereferenced (except
> for binding an array to an array reference, etc.). Transparent
> references always automatically dereference. The decision of what
> type of dereferencing will go on is left up to
Juerd skribis 2005-05-28 1:15 (+0200):
> There are named arrays, @foo, and anonymous arrays, [].
>
> There are named hashes, %foo, and anonymous hashes, {}.
>
> There are only anonymous pairs. You can't dereference a pair, or bind a
> name to it.
I forgot an important one:
There are named sca
Fri May 27 15:45:12 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
* export withArgs from Main
New patches:
[export withArgs from Main
Samuel Bronson <[EMAIL PROTECTED]>**20050527194512] {
hunk ./src/Main.hs 17
-module Main where
+module Main (module Main, withArgs) where
}
Context:
[r3981
<[EM
Um, don't worry about this one. I sent it in before I got commit access.
On 27/05/05, Samuel Bronson <[EMAIL PROTECTED]> wrote:
> Fri May 27 15:45:12 EDT 2005 Samuel Bronson <[EMAIL PROTECTED]>
> * export withArgs from Main
On 5/27/05, Juerd <[EMAIL PROTECTED]> wrote:
>
> There is no way to get an anonymous rw scalar, is there?
Can't the [] and {} syntaxes be considered aliases for new Array(...)
and new Hash(...)?
my $x := new int = 10; # looks like it should work
Ashley Winters
In regards to http://www.nntp.perl.org/group/perl.perl6.language/21120
which discusses character class syntax in Perl 6, I have some comments to
make.
First, I've been very interested in seeing proper set notation for char
classes in Perl 5. I was pretty vocal about it during TPC in 2002, I
Thanks very much to Matt for his recent checkins, cleaning up tclparser.pmc,
and eliminating a bit of unnecessary code.
The compiler broke after some recent checkins (not Matt's fault). I've added a
test for this which is now passing, which should hopefully *keep* it passing.
=-)
With Matt's
Juerd <[EMAIL PROTECTED]> wrote:
> There is no way to get an anonymous rw scalar, is there?
There's always the Perl 5 hack:
\do { my $x }
Although that's not truly anonymous, I suppose.
--
Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]>
Perl and Parrot hacker
52 matches
Mail list logo
