The S29 Functions Project
flag
Messages 21 - 26 of 26 - Collapse all
/groups/adfetch?adid=WN8b4hEAAADQcCQZi7tSE1cJoPvzzKT0FSRgCP-avRN4YT0eROC0jw
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
21.  Rod Adams  
View profile  
 More options Mar 14 2005, 1:16 pm
Newsgroups: perl.perl6.language
From: r...@rodadams.net (Rod Adams)
Date: Mon, 14 Mar 2005 12:16:13 -0600
Local: Mon, Mar 14 2005 1:16 pm
Subject: Re: The S29 Functions Project

What I'm thinking of doing is creating a soft rule of:
    You can't declare a function into ::*. You have to create it
elsewhere, and bind it in.

Therefore, as I go through S29, I'll assign all functions to some
module. I'll be using the P5/CPAN hierarchy as a strong guideline.

We can then discuss what gets bound into ::*, and when, at some later
point in time.

-- Rod Adams


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
22.  Larry Wall  
View profile  
 More options Mar 14 2005, 1:36 pm
Newsgroups: perl.perl6.language
From: la...@wall.org (Larry Wall)
Date: Mon, 14 Mar 2005 10:36:06 -0800
Local: Mon, Mar 14 2005 1:36 pm
Subject: Re: The S29 Functions Project
On Mon, Mar 14, 2005 at 12:16:13PM -0600, Rod Adams wrote:

: Therefore, as I go through S29, I'll assign all functions to some
: module. I'll be using the P5/CPAN hierarchy as a strong guideline.
:
: We can then discuss what gets bound into ::*, and when, at some later
: point in time.

That's an excellent idea.  We can encourage people to write the qualified
name if they want to be future-proof past the 6.0.0 boundary.

Larry


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
23.  Nicholas Clark  
View profile  
 More options Mar 15 2005, 2:59 pm
Newsgroups: perl.perl6.language
From: n...@ccl4.org (Nicholas Clark)
Date: Tue, 15 Mar 2005 19:59:52 +0000
Local: Tues, Mar 15 2005 2:59 pm
Subject: Re: The S29 Functions Project

On Mon, Mar 14, 2005 at 08:59:32AM -0800, Larry Wall wrote:
> On Mon, Mar 14, 2005 at 08:10:15AM -0600, Patrick R. Michaud wrote:
> : I ran into this problem while creating a mini-list of S29 functions
> : (which Rod's work supercedes, I suspect, and I'm very glad he's taking
> : this on).  What are some guidelines we could use in deciding
> : which functions are automatically in ::* ?  Or is this just a case
> : where we need to use past experience and best guesses as our guide?
>   * Another confounding factor is that memes tend to come in bundles,
>     and you'd kind of like to keep the bundles together.  So my earlier
>     question really amounted to whether POSIX was really a valid
>     bundle of memes.  (Probably not.)  On the other hand, the trig
>     functions might well be a valid bundle, and we might want to
>     keep them all together either in * or Trig.

To me it seems that a there are some groups of core builtins in Perl 5
that group conceptually quite well, and it's sensible to remove en mass,
which are the builtins that aren't really useful in Perl 5 without loading
an extension module. So all the socket related builtins aren't much use
without the constants exported by Socket; and the System V IPC builtins
aren't much use without the IPC::SysV, so they could quite easily be
exported by that instead.

But then it gets less obvious what other groups from the top of perlfunc.pod
might manage a discrete exit from ::* without anyone noticing. So, no, I
don't have an answer :-)

Nicholas Clark


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
24.  Rod Adams  
View profile  
 More options Mar 15 2005, 3:25 pm
Newsgroups: perl.perl6.language
From: r...@rodadams.net (Rod Adams)
Date: Tue, 15 Mar 2005 14:25:01 -0600
Local: Tues, Mar 15 2005 3:25 pm
Subject: Re: The S29 Functions Project
At 07:59 PM 3/15/2005 +0000, you wrote:

I've put the following note at the top of S29.pod (in an update I haven't
posted yet).

In Perl 6, all builtin functions belong to a named package. Not all
functions are guaranteed to be imported into the global package
C<::*>. In addition, the list of functions imported into C<::*> will be
subject to change with each release of Perl. Authors wishing to
"Future Proof" their code should either specifically import the
functions they will be using, or always refer to the functions by their
full name.

-- Rod Adams


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
25.  Larry Wall  
View profile  
 More options Mar 15 2005, 6:52 pm
Newsgroups: perl.perl6.language
From: la...@wall.org (Larry Wall)
Date: Tue, 15 Mar 2005 15:52:32 -0800
Local: Tues, Mar 15 2005 6:52 pm
Subject: Re: The S29 Functions Project
On Tue, Mar 15, 2005 at 02:25:01PM -0600, Rod Adams wrote:

: In Perl 6, all builtin functions belong to a named package. Not all
: functions are guaranteed to be imported into the global package
: C<::*>. In addition, the list of functions imported into C<::*> will be
: subject to change with each release of Perl. Authors wishing to
: "Future Proof" their code should either specifically import the
: functions they will be using, or always refer to the functions by their
: full name.

Hmm, what I said was supposed to be policy for just the development
release of 6.0.0.  However, it's not that far off from the general
case if you add something along the lines of:

    After 6.0.0 comes out, global aliases will not be removed lightly,
    and will never be removed at all without having gone through a
    deprecation cycle of at least a year.  In any event, you can specify
    that you want the interface for a particular version of Perl, and
    that can be emulated by later versions of Perl to the extent that
    security updates allow.

Interestingly, that last sentence means that different modules can
have different views of * space.  But really, that just falls out
of ordinary module versioning, if you can warp your brain around to
thinking of * as an ordinary versioned module.  The long name of *
just happens to include the Perl version number, and could presumably
even include different "authors" if we ever fork Perl.

Larry


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
26.  Rod Adams  
View profile  
 More options Mar 15 2005, 7:07 pm
Newsgroups: perl.perl6.language
From: r...@rodadams.net (Rod Adams)
Date: Tue, 15 Mar 2005 18:07:12 -0600
Local: Tues, Mar 15 2005 7:07 pm
Subject: Re: The S29 Functions Project

"Add something along the lines of" was interpreted as "clip and paste into S29.pod".

I wasn't meaning to imply that bindings would be changed willy-nilly in production, but I can see how that could be inferred from what I wrote. My main intention was that it *could* change over time.

These whole paragraphs can be reworded later, possibly at the same time we sit down and figure out the policy of what gets imported into *:: when.

-- Rod Adams


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google