develooper Front page | perl.perl6.language | Postings from July 2001

Re: Per-object inheritance in core a red herring?

Thread Previous | Thread Next
From:
schwern
Date:
July 1, 2001 12:51
Subject:
Re: Per-object inheritance in core a red herring?
Message ID:
20010701155130.B17494@magnonel.guild.net
On Sun, Jul 01, 2001 at 01:07:59AM -0400, Dan Sugalski wrote:
> >*buzzzz* false logic.  If you can do something via a core module, it
> >is supported by Perl.  Or does Perl not do CGI, web stuff, databases,
> >etc...?
> 
> Wrong--you may have a terrifically hard time using perl modules to provide 
> functions for non-perl languages that the interpreter supports. It may not 
> help Python, or Ruby, for example, that libnet or its equivalent are 
> provided as part of perl 6.

Huh??


> >Anyhow, Self is the only one I can think of.  ALL THE FULL-TIME SELF
> >PROGRAMMERS HERE, PLEASE RAISE THEIR HANDS! ;)
> 
> So? Find all the folks that use languages that provide curried functions 
> full-time.

There's two things in combination going on here.  1) The feature is
obscure.  2) The feature is easy and fairly efficient to implement
outside of Perl 6.  That's the rough criterion I'm using for
determining if something should or should not be in the core.

Curried functions, AFAIK, only have the first trait.  Then again, I
really don't understand curried functions.  If it turns out they have
both traits, maybe we should relegate them to a core module instead.


-- 
Michael G Schwern   <schwern@pobox.com>   http://www.pobox.com/~schwern/
Perl6 Quality Assurance     <perl-qa@perl.org>       Kwalitee Is Job One

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About