Damian Conway wrote:
> we could make it lazy thus:
>
> sub a_pure_func(Num $n) is lazy returns Num {
> return $n ** $n
> }
>
> which would cause any invocation of C to cache
> its arguments (probably in a closure) and return a "proxy"
> Num that carries out the computation on
Andy Dougherty (via RT) wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #18189]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18189 >
Not OK: This is a failure report for parrot.
When bu
Billy Naylor asked:
Would it be useful to apply memoization in a similar fashion...
sub square ( Num $n ) is memo {
return $n ** $n;
}
Yes. Larry indicated this in A2
(see http://search.cpan.org/perl6/apo/A02.pod#Properties).
The name of the property is still under debate. Larry favours:
Luke Palmer wrote:
sub a_pure_func(Num $n) returns Num {
class is Num {
method FETCH { $n * $n } }.new
}
Yes? No?
Not quite.
> sub a_pure_func(Num $n) returns Num {
> class is Num {
> has Num $cache;
> method FETCH { $cache //
Larry Wall wrote:
... I can see ways of binding properties
to a location without growing the location itself, but I think stuffing
a junction of ints into a single location is somewhat problematical.
We are still talking about native types - these with lowercase names in
the docs? Why should
Rx had some time ago (~0.0.6) a state structure rxinfo. AFAIK this was
tossed for speed reasons, state is kept in registers now.
This has several impacts:
- regexen are not reentrant anymore (global intstack)
- they don't/can't manage their allocated resources like bitmaps
1) I would propose, tha
At 8:02 on 11/08/2002 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Josh Wilmes wrote:
>
> > For the meantime, I have added the Parrot_exit and Parrot_on_exit function
s
> > to CVS.
>
> Thanks for providing this. I did slightly modify your patch to really
> get rid of the leaks:
> - test
Leopold Toetsch:
# 2) For bitmaps I would provide a bitlist.c with functions for setting
# and testing bits. This bitlist would be based on list, so it
# should be
# fast enough and had no limits WRT unicode chars.
Note that the "Bitmaps" used by rx are only bitmaps within US-ASCII, to
keep siz
Brent Dax wrote:
> Leopold Toetsch:
> # 2) For bitmaps I would provide a bitlist.c with functions for setting
> # and testing bits. This bitlist would be based on list, so it
> # should be
> # fast enough and had no limits WRT unicode chars.
>
> Note that the "Bitmaps" used by rx are only bitmaps
On Fri, Nov 08, 2002 at 08:22:17PM +1100, Damian Conway wrote:
> Billy Naylor asked:
>
> > Would it be useful to apply memoization in a similar fashion...
> >
> > sub square ( Num $n ) is memo {
> > return $n ** $n;
> > }
>
> Yes. Larry indicated this in A2
> (see http://search.cpan.org/
On Fri, Nov 08, 2002 at 03:04:16PM +, Nicholas Clark wrote:
> On Fri, Nov 08, 2002 at 08:22:17PM +1100, Damian Conway wrote:
> > The name of the property is still under debate. Larry favours:
> >
> > sub square ( Num $n ) is same {...}
> >
> > whereas others feel that:
> >
> > sub sq
On Thursday, November 7, 2002, at 10:45 PM, Piers Cawley wrote:
Those of us with subs to perl6-all will get this anyway, right?
I posted an initial message about five minutes ago, so if you received
it, then yes. :-)
MikeL
On 8 Nov 2002 at 9:12, Michael Lazzaro wrote:
>
> On Thursday, November 7, 2002, at 10:45 PM, Piers Cawley wrote:
> > Those of us with subs to perl6-all will get this anyway, right?
>
> I posted an initial message about five minutes ago, so if you received
> it, then yes. :-)
There are few m
> Date: Fri, 8 Nov 2002 15:04:16 +
> From: Nicholas Clark <[EMAIL PROTECTED]>
>
> And to people in the perl5 know, Memoize is the module that implements this,
> hence why people who know of how and what Memoize can do favour that name.
> Except that it's not necessarily obvious to everyone else
Luke Palmer:
# What's wrong with C?
#
# C ain't bad either, but it won't appeal to
# non-mathematicians---even certain kinds of mathematicians.
# Mathematica thinks a "pure" function is what we think of as
# an "anonymous" sub. So I like C.
How about C, in an analogy to physics?
steady state
On Fri, Nov 08, 2002 at 12:12:53PM -0700, Luke Palmer wrote:
> What's wrong with C?
>
> C ain't bad either, but it won't appeal to
> non-mathematicians---even certain kinds of mathematicians.
> Mathematica thinks a "pure" function is what we think of as an
> "anonymous" sub. So I like C.
Part o
On Fri, Nov 08, 2002 at 05:30:00PM +0100, Paul Johnson wrote:
> On Fri, Nov 08, 2002 at 03:04:16PM +, Nicholas Clark wrote:
> > On Fri, Nov 08, 2002 at 08:22:17PM +1100, Damian Conway wrote:
> > > The name of the property is still under debate. Larry favours:
> > >
> > > sub square ( Num $n
Jonathan Scott Duff wrote:
On Fri, Nov 08, 2002 at 05:30:00PM +0100, Paul Johnson wrote:
On Fri, Nov 08, 2002 at 03:04:16PM +, Nicholas Clark wrote:
On Fri, Nov 08, 2002 at 08:22:17PM +1100, Damian Conway wrote:
The name of the property is still under debate. Larry favours:
sub square
On Fri, Nov 08, 2002 at 11:41:38AM -0800, Brent Dax wrote:
> Luke Palmer:
> # What's wrong with C?
> #
> # C ain't bad either, but it won't appeal to
> # non-mathematicians---even certain kinds of mathematicians.
> # Mathematica thinks a "pure" function is what we think of as
> # an "anonymous"
I still prefer "cached", which sounds less lingo-ish than "memoized" but reads
better than "same" ("Same as what?").
> Billy Naylor asked:
>
> > Would it be useful to apply memoization in a similar fashion...
> >
> > sub square ( Num $n ) is memo {
> > return $n ** $n;
> > }
>
> Yes. La
Paul Johnson <[EMAIL PROTECTED]> writes:
> On Fri, Nov 08, 2002 at 12:12:53PM -0700, Luke Palmer wrote:
>
>> What's wrong with C?
>>
>> C ain't bad either, but it won't appeal to
>> non-mathematicians---even certain kinds of mathematicians.
>> Mathematica thinks a "pure" function is what we think
"Markus Laire" <[EMAIL PROTECTED]> writes:
> On 8 Nov 2002 at 9:12, Michael Lazzaro wrote:
>
>>
>> On Thursday, November 7, 2002, at 10:45 PM, Piers Cawley wrote:
>> > Those of us with subs to perl6-all will get this anyway, right?
>>
>> I posted an initial message about five minutes ago, so if
On Friday, November 8, 2002, at 07:03 AM, Adam D. Lopresto wrote:
I still prefer "cached", which sounds less lingo-ish than "memoized"
but reads
better than "same" ("Same as what?").
Insert obligatory reference to Eiffel here, which IIR uses the word
"once":
sub square ( Num $n ) is same
>Ah... that would explain why I haven't seen it then. Looks like
>someone broke perl6-all.
No, it was just "not configured".
Future messages to perl6-documentation should end up on perl6-all.
-R
Robert Spier <[EMAIL PROTECTED]> writes:
>>Ah... that would explain why I haven't seen it then. Looks like
>>someone broke perl6-all.
>
> No, it was just "not configured".
>
> Future messages to perl6-documentation should end up on perl6-all.
Good oh.
--
Piers
"It is a truth universally ac
Michael Lazzaro wrote:
On Friday, November 8, 2002, at 11:07 AM, Richard Nuttall wrote:
I presonally use a combination of documentation for programming, and
find the Perl documentation more difficult to use than many.
That's an interesting observation -- I'd love to hear more thoughts on
t
Here's some notes based on the first bits of feedback -- something to
throw rocks at, as it were.
"The overall project goal is to produce documentation that will:"
(1) define precise semantics for the Perl6 language; discover and
document ambiguous possible behaviors and report them to the desi
[diverting to p6-doc]
Luke Palmer wrote:
> As for your documentation plan, I think it's a good idea, though I
> concur with Dan on Just Do It. Document the language for what best
> makes sense now. If there are *big* issues, ask Larry et al. on this
> list. For the little ones, use common sense
28 matches
Mail list logo
