Stephane Peiry <[EMAIL PROTECTED]> wrote:
> ow.. ok, this one is actaully a macro.. the actual function is
> gulong g_signal_connect_object (gpointer instance,
> const gchar *detailed_signal,
> GCallback c_handler,
>
Matt Fowles <[EMAIL PROTECTED]> wrote:
> All~
> I was thinking about reworking the Parrot build system to use scons
> (http://www.scons.org/). The up side to this is that it would allow
> more precise dependecies and could probably be used to eliminate the
> configure step. The down side is that
Steve Fink <[EMAIL PROTECTED]> wrote:
> I needed to create a Match PMC object for holding the match groups
> (parenthesized expressions and capturing rules) from a regex match.
> Unfortunately, it works by using another new PMC type, the MatchRange
> PMC,
> .. One PMC knowing about
> another curr
On Wed, Aug 18, 2004 at 09:21:22AM +0200, Leopold Toetsch said:
> Rather not. Python is AFAIK not as portable as Perl. But there is a Perl
> based make somewhere, the named just escaped my mind.
It's called Cons. I can't remember whether Cons or Scons came first
(ah, Cons was the orginal http://
Simon Wistow wrote:
Leopold Toetsch said:
Rather not. Python is AFAIK not as portable as Perl. But there is a Perl
based make somewhere, the named just escaped my mind.
It's called Cons. I can't remember whether Cons or Scons came first
(ah, Cons was the orginal http://www.scons.org/faq.html#SS_6
At 12:40 PM -0400 8/16/04, Dan Sugalski wrote:
I should [TODO] this, but I think it might get lost in the recent
blast 'o TODO items. (All of which I'd be thrilled if someone took
on. A big thanks to Will for diving into the queue and website and
getting things in a semblance of order)
This one
At 5:53 PM -0700 8/17/04, Brent 'Dax' Royal-Gordon wrote:
Michel Pelletier <[EMAIL PROTECTED]> wrote:
if Perl or other languages want an undef returned, it would seem to make
more sense that they assume to cost of catching the exception and
turning it into an undef, than everyone else turning th
At 6:20 PM -0400 8/17/04, Aaron Sherman wrote:
On Tue, 2004-08-17 at 16:22, Felix Gallo wrote:
On Tue, Aug 17, 2004 at 04:08:34PM -0400, Dan Sugalski wrote:
> 1) We're going to have MMD for functions soon
> 2) Function invocation and return continuation invocation's
> essentially identical
> 3
On Wed, Aug 11, 2004 at 01:10:42AM -0400, Dan Sugalski wrote:
>
> >A good place to look at for the complete list is Perl 5's system
> >abstraction layer.
>
> Yeah. If you've got time to get a list I'd very much appreciate it.
http://search.cpan.org/src/NWCLARK/perl-5.8.5/iperlsys.h
Tim.
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Rather not. Python is AFAIK not as portable as Perl. But there is a Perl
> based make somewhere, the named just escaped my mind.
We use Makepp (http://makepp.sourceforge.net/) here. Written in Perl, its
particular stre
On Wed, 2004-08-18 at 10:06, Dan Sugalski wrote:
> Yep, though the error dispatch case is definitely the easy one. Where
> it gets fun is:
>
> sub foo :come_from('bar', int) {
You've created an MMD come-from
Uh... that hurts.
I think using it for type-based, switch-like dispatch would
This bit comes from the p6i list, and I just thought I'd ask those
in-the-know if my suggested "returntype" role/property would make sense
here, or if there's another way to do it that makes more sense?
For that matter, does MMD on return type map into Perl6's gestalt at
all, or would it be tumoro
Aaron Sherman wrote:
This bit comes from the p6i list, and I just thought I'd ask those
in-the-know if my suggested "returntype" role/property would make sense
here, or if there's another way to do it that makes more sense?
For that matter, does MMD on return type map into Perl6's gestalt at
all, o
I think this is something the optimizer could use to eliminate an
"ordinary" return that happens to be followed by a call to a known
set of something elses. So it might well help things like switch
statements and cascaded function calls and tail recursion (and maybe
invocation of autoloaded functi
At 11:33 AM -0400 8/18/04, Aaron Sherman wrote:
On Wed, 2004-08-18 at 10:06, Dan Sugalski wrote:
Yep, though the error dispatch case is definitely the easy one. Where
it gets fun is:
sub foo :come_from('bar', int) {
You've created an MMD come-from
Uh... that hurts.
Yes, but imagine the p
Dan writes:
> sub foo :come_from('+', int, int) {}
One problem with MMD in general, and return specifically, is
'what happens if multiple M match the same D requirements?
i.e.,
sub foo :come_from('+', int, int) { shift; shift builtin::+ shift };
sub bar :come_from('+', int, int) { shift; shi
On Wed, Aug 18, 2004 at 09:11:17AM +0200, Leopold Toetsch wrote:
> You've mixed up the function parameters.
>
> > P0 = global "Gtk::gtk_window_new"
> > null I5
> > invoke
>
> > P15 = P5
>
> I presume that's "instance" ...
actually shouldnt the callback is for the button
> > # -- funct
On Wed, 2004-08-18 at 15:57, Felix Gallo wrote:
> Dan writes:
> > sub foo :come_from('+', int, int) {}
>
> One problem with MMD in general, and return specifically, is
> 'what happens if multiple M match the same D requirements?
> i.e.,
That's a question, not a problem. It's easy to answer q
On Sat, Aug 14, 2004 at 08:57:21AM -0700, Larry Wall wrote:
: You'll also want to make sure the zip operator (¥) gets in there,
: probably with the same precedence as ==> (unless we decide it's
: a scalar-only operator, in which case it can be tighter because it
: would only work on array refs). I
Aaron writes:
> Ok, this is starting to look like people speaking seriously about using
> Intercal's COME FROM (http://c2.com/cgi/wiki?ComeFrom)... can we just
> step back and take a deep breath of AIR please? Seriously, this is
> starting to creep me out.
In case anyone reading this is getting co
Larry Wall skribis 2004-08-18 15:37 (-0700):
> It the moment the zipper has moved to be the same precedence as comma,
> because it really wants to be looser than ranges but tighter than
> listops. Plus it's sort of like a »,« if you squint. I'm eagerly
> awaiting my first opportunity to use the »
# New Ticket Created by Will Coleda
# Please include the string: [perl #31229]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31229 >
Index: build_tools/c2str.pl
==
At 3:57 PM -0400 8/18/04, Felix Gallo wrote:
Dan writes:
sub foo :come_from('+', int, int) {}
One problem with MMD in general, and return specifically, is
'what happens if multiple M match the same D requirements?
Well... usually what happens is that an ambiguous function error is
thrown. I c
On Sat, 14 Aug 2004, Larry Wall wrote:
> To get a Perlish representation of any data value, use the C<.repr>
> method. This will put quotes around strings, square brackets around
> list values, curlies around hash values, etc., such that standard
> Perl could reparse the result. XXX .repr is what
On Wed, Aug 18, 2004 at 10:02:57PM -0600, John Williams wrote:
: On Sat, 14 Aug 2004, Larry Wall wrote:
: > To get a Perlish representation of any data value, use the C<.repr>
: > method. This will put quotes around strings, square brackets around
: > list values, curlies around hash values, etc.,
On 8/14/04, [EMAIL PROTECTED] (Larry Wall) wrote:
>To get a Perlish representation of any data value, use the C<.repr>
>method. This will put quotes around strings, square brackets around
>list values, curlies around hash values, etc., such that standard
>Perl could reparse the result. XXX .rep
Felix Gallo wrote:
Aaron writes:
Ok, this is starting to look like people speaking seriously about using
Intercal's COME FROM (http://c2.com/cgi/wiki?ComeFrom)... can we just
step back and take a deep breath of AIR please? Seriously, this is
starting to creep me out.
Aspect Oriented Program
Aaron writes:
> COME FROM is very different, and (as with much of Intercal) was created
> specifically to be obtuse. Discussing it as if it's a useful feature
> tends to creep me out because I get the feeling someone might actually
> put it in a language I care about.
I feel the same way about
28 matches
Mail list logo
