Adam Turoff writes:
> On Sun, Jun 01, 2003 at 10:44:02PM -0600, Luke Palmer wrote:
> > It will still have a lot of power in text processing, and still be a
> > powerful "quicky" language, but that's no longer its primary focus --
> > not to say that highly structured programming is. Some applicati
On Mon, Jun 02, 2003 at 10:34:14AM -0600, Luke Palmer wrote:
> What it seems you're wanting is it to be in the core. And I'm saying
> that's irrelavent. There are thousands of great ideas out there, and
> they can't all fit into Perl's core. That's why there's thousands of
> modules on CPAN.
H
Michael Lazzaro <[EMAIL PROTECTED]> writes:
> On Monday, May 26, 2003, at 06:10 PM, Dave Whipp wrote:
>> So, in summary, its good to have a clean abstraction for all the
>> HCCCT things. But I think it is a mistake to push them too
>> close. Each of the HCCCT things might be implemented as facades
On Mon, Jun 02, 2003 at 10:34:14AM -0600, Luke Palmer wrote:
> And I don't see what's stopping someone from writing Dispatch::Value.
>
> use Dispatch::Value;
> sub foo($param is value('param1')) {...}
> sub foo($param is value('param2')) {...}
>
> What it seems you're wanting is it to
> A better fitting solution wouldn't focus on classic
> MMD, but simply "Dispatch", where type- and value-based
> dispatching are two of many kinds of dispatching supported.
I've always liked the sound of Linda's tuple spaces
and view that as a nice generalized dispatch approach.
Procedure calls
> A better fitting solution wouldn't focus on classic
> MMD, but simply "Dispatch", where type- and value-based
> dispatching are two of many kinds of dispatching supported.
I've always liked the sound of Linda's tuple spaces
and view that as a nice generalized dispatch approach.
Procedure calls
Piers Cawley wrote:
>
> The Perl 6 Summary for the week ending 20030601
> Another Monday, another Perl 6 Summary. Does this man never take a
> holiday? (Yes, but only to go to Perl conferences this year, how did
> that happen?)
>
> We start with the internals list as usual.
>
>
On Mon, 2 Jun 2003, Benjamin Goldberg wrote:
> All values needing timely destruction would inherit from a class
> RefCounted.
I like this concept a lot, but maybe we can take it a little further and
make it transparent to the programmer. Suppose that the internals only
tracked objects that have
Luke Palmer wrote:
I think it would fall trivially out of the events mechanism, which is
planned for Parrot.
I have heard rumours of such a thing, but no details of how it will be
exposed in the language...
Dave.
I have a working implementation that that switches parrot to a continuation
passing style. While working on cleaning up a few things up, I got the
following idea ...
The current parrot context struct has a set of register stacks
struct IRegChunk *int_reg_top;
struct NRegChunk *num_reg_top
A small annoyance, I can't seem to write a good line-input routine as of
very recent changes (synced yesterday, noon). All I'm trying to do is
variations on:
print "? "
readline S0, 0
And no prompt shows before the readline starts its business. Any
suggestions as to how I can
"Piers Cawley" <[EMAIL PROTECTED]> wrote
> Threads and Progress Monitors
> Dave Whipp had some more thread questions, and wondered what would be
a
> good Perl 6ish way of implementing a threaded progress monitor. Whilst
> the discussion of all this was interesting, I'm not sure that i
> "Piers Cawley" <[EMAIL PROTECTED]> wrote
> > Threads and Progress Monitors
> > Dave Whipp had some more thread questions, and wondered what would be
> a
> > good Perl 6ish way of implementing a threaded progress monitor. Whilst
> > the discussion of all this was interesting, I'm not
Luke Palmer <[EMAIL PROTECTED]> wrote:
> It appears JIT is entirely broken. It broke recently, as it was
> working well for me just a couple days ago.
> I'm running i686 (P3) Linux, gcc-3.2.2
Have it. I did install gcc 3.3.1 (and a newer gdb). The segfaults are
due to new ways how gcc 3 does su
Clinton A. Pierce <[EMAIL PROTECTED]> wrote:
> A small annoyance, I can't seem to write a good line-input routine as of
> very recent changes (synced yesterday, noon). All I'm trying to do is
> variations on:
> print "? "
> readline S0, 0
> And no prompt shows before the readline sta
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [perl #22521]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22521 >
I'm not sure what triggers this bug, but I can reliably reproduce it. The
code
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> I'd like to reiterate (and clarify) my idea, of a hybrid scheme
> combining refcounting and DoD.
I'll try to translate this to parrot speak. I hope that I fully
understand your scheme, but lets see.
> All values needing timely destruction would inhe
Clinton A. Pierce <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by "Clinton A. Pierce"
> # Please include the string: [perl #22521]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=22521 >
> I'm not sure what triggers t
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #22535]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22535 >
Hi,
In many places in the code we use the idiom
PIO_fprintf(interpreter, PIO_STDERR(i
Hello.
MSVC stumble over
static struct longopt_opt_decl options[] = {
.
{'\0', 128, 0, { "--gc-debug" } },
{'\0', 0, 0, { } }
}
Рlease, replace it by
RCS file: /cvs/public/parrot/test_main.c,v
retrieving revision 1.66
diff -r1.66 test_main.c
36c36
< {'\0', 0, 0,
> Hello.
>
> MSVC stumble over
>
> static struct longopt_opt_decl options[] = {
> .
> {'\0', 128, 0, { "--gc-debug" } },
> {'\0', 0, 0, { } }
> }
>
> Рlease, replace it by
>
> RCS file: /cvs/public/parrot/test_main.c,v
> retrieving revision 1.66
> diff -r1.66 test_main
On Tue, 2003-06-03 at 03:54, Henrik Tougaard wrote:
> On Sat, May 31, 2003 at 09:54:45AM -0400, Bryan C. Warnock wrote:
> [snip]
Part of what was snipped was this line:
(For the sake of using real numbers, I'll assume 32/64.)
> > Currently, the flow is, in variable sizes:
> >
> > Opcod
At 11:10 PM 6/1/2003 -0400, Uri Guttman wrote:
why don't you manage your own basic call stack in an array or PerlArray
or something? trying to map that mess of call/return poo onto a proper
compiler with register allocation is going to lose us the services of
leo while he recuperates at the hospita
"Sean O'Rourke" <[EMAIL PROTECTED]> writes:
> On 30 May 2003, Bryan C. Warnock wrote:
>> Ha ha, just kidding, of course. I'm all for it, but given my record
>> today, that might be an imminent sign of its rejection.
>
> Or, given your historical record, you may have just killed the thread ;).
Th
The Perl 6 Summary for the week ending 20030601
Another Monday, another Perl 6 Summary. Does this man never take a
holiday? (Yes, but only to go to Perl conferences this year, how did
that happen?)
We start with the internals list as usual.
More on timely destruction
The dis
25 matches
Mail list logo
