> "Dave" == Dave Storrs <[EMAIL PROTECTED]> writes:
Dave> When you want to install a new version, you simply prepend it
Dave> with its version number (or insert it at appropriate place).
Dave> The order is, of course, irrelevant...you can order it as 1.3,
Dave> 2.0, 1.0 if you want, but the
Adam Turoff wrote:
>
> On Wed, Sep 27, 2000 at 11:33:13AM -0700, Nathan Wiger wrote:
> > Ziggy, are you interested in this idea enough (at all?) to stick a note
> > about the 'header' function into the RFC? Or should I RFC it separately?
>
> Adding headers() to the core language (or a similar pr
Perl6 RFC Librarian wrote:
>
> =head1 ABSTRACT
>
> Perl is frequently used in CGI environments. It should be as easy to write
> CGI programs with perl as it is to write commandline text filters.
>
> =head1 DESCRIPTION
>
> Tom Christiansen proposed this in his perl6storm message:
>
>
> =head1 ABSTRACT
>
> Pseudo-hashes and the associated fields pragma shoule be removed from
> Perl 6.
A few counter points:
Removal of pseudo-hashes should not stop us from using this (or a
similar mechanism) under the covers in perl6 to implement strongly typed
objects.
AFAIK, most of the pai
Nathan Wiger wrote:
>
> > I think such modules are a bad idea, because their functionality is
> > typically restricted.
>
> What, you mean like CGI.pm ?! :-)
Yes, restricted. If you use the procedural interface to a module that
supports both OO and procedural interfaces, you're basically at th
John Porter wrote:
>
> Hildo Biersma wrote:
> >
> > I think such modules are a bad idea, because their functionality is
> > typically restricted.
>
> Oh? Where do you get that idea?
Think about it. If a module supports both an OO and a procedural
interface, t
Nathan Wiger wrote:
> >
> > and this may, indeed, be sufficient.
>
> Remember, this still won't solve the problem of a module whose functions
> can handle both OO and function-oriented calls - and yes, I have many
> that do this. :-)
I think such modules are a bad idea, because their functional
"David L. Nicol" wrote:
>
> Hildo Biersma wrote:
> >
> > > =head1 ABSTRACT
> > >
> > > Herein a new syntax is introduced to specify a sort function
> > > for the keys of any hash.
> > >
> > > =head1 DESCRIPTION
>
> =head1 ABSTRACT
>
> Herein a new syntax is introduced to specify a sort function
> for the keys of any hash.
>
> =head1 DESCRIPTION
>
> %professors{ $a->name cmp $b->name };
I feel the sort order should be specified on the iterator, not on the
hash variable. It should be possible to
"David L. Nicol" wrote:
>
> What if its a method of anything in an array? $_ is already
> a reference to the object on the array in for loops rather
> than a copy of it. What if we make change be not something about
> for loops, but about anything in an array?
>
> print "The index, in
> =head1 DESCRIPTION
>
> Many other programs have so called "resource configuration" files (at
> least that's what I call them) that are loaded and interpretted upon
> program startup. Some example programs that have this ability include
> bash, mutt, and python. Perl should do the same.
>
> A
Steve Simmons wrote:
>
> On Wed, Aug 16, 2000 at 08:03:31PM -, Perl6 RFC Librarian wrote:
>
> > Perl should provide a mechanism to have common code autoloaded from a
> > file. . . .
>
> > A C file could be used to set system-wide defaults that
> > the system administrator would like to prom
> =head1 TITLE
>
> Replace => (stringifying comma) with => (pair constructor)
>
> =head1 VERSION
>
> Maintainer: Damian Conway <[EMAIL PROTECTED]>
> Date: 10 August 2000
> Version: 1
> Mailing List: [EMAIL PROTECTED]
> Number: 84
I like this a lot, especially the way it deals with s
John Porter wrote:
>
> Michael Fowler wrote:
> >
> > I think a stringified reference is worth seeing, moreso than a simple undef,
> > for debugging purposes if nothing else.
>
> I personally would like to have the stringification of refs be a
> symmetric operation, i.e. such a string should dwim
>
> =head1 TITLE
>
> All Perl core functions should return objects
>
Yuck. Why not use the proposed want() and return hash-refs or slices,
when appropriate.
Hildo
> =head1 TITLE
>
> Higher order functions
Sounds good. We should add this to the language. Oh boy, the tricks we
can play with this...
Hildo
> =head1 DESCRIPTION
>
> Making what's changed in documentation stand out's quite useful,
> something I'm coming to appreciate more and more as the RFCs are
> flying back and forth. The standard way to do this is to mark the
> changed sections with one or more vertical bars on the left margin.
>
Bennett Todd wrote:
>
> There are many intents and points to this project. As _I_ see them,
> they include, in no particular order:
>
> - cleaning up the language definition, where practical without
> losing the distinctive appeal of perl to happy perl programmers;
>
> - cleaning up the imple
Ed Mills wrote:
>
> I actually saw this in the newsgroups and thought it was a neat idea. What
> about
>
>println $textvar;
>
> instead of
>
>print "$textvar\n";
>
> Ever so much easier to read and write, prints the arg and appends \n.
This is probably what I disliked most about Pasc
Peter Scott wrote:
>
> Have often wanted a way to tell whether a scalar was a number, and rolling
> a regex each time seemed wasteful given that Perl knew what it was
> anyway. So a user-friendly way to get at the SvIOK and SvNOK results would
> be great.
>
> The pedestrian way would be a built
Perl6 RFC Librarian wrote:
>
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Operators: Polymorphic comparisons
>
> =head1 VERSION
>
> Maintainer: Damian Conway <[EMAIL PROTECTED]>
> Date: 7 August 2000
> Version: 1
> Mailing List: [
Perl6 RFC Librarian wrote:
>
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Built-ins: Merge and generalize C and C
>
Sounds good - but having both the third and fourth arguments feel
counter-intuitive to me. It certainly seems relatively
Leon Brocard wrote:
>
> Perl6 RFC Librarian sent the following bits through the ether:
>
> > affected files. I suggest that in a list context, they return the I
> > of the I affected files.
>
> This seems the wrong way around to me. Surely it should instead return
> the name of the successfull
Johan Vromans wrote:
> You missed the point.
>
> If you need 6+ lines of code for each elementary error check, this is
> what is going to happen (and it _does_ happen in almost every Java
> program I've seen):
>
> try {
>open file
>while read a record
> process its
Damian Conway wrote:
>
> One of my many RFCs will include a proposal for a $SELF variable along
> those lines.
Before it's too late - please, don't impose either '$self' or '$this',
but make this a per-module choice. I deal with people of both these
religions...
Hildo
Steve Simmons wrote:
>
> Summary:
>
> There is no circumstance in which I have had to do `no strict.'
>
I have had a need for symbolic references - unless you want to do 'eval'
which could be worse...
Basically, I am parsing messages, where every message has a distinct
numbe rof logical field
Matt Sergeant wrote:
>
> [I might join perl6-language some day, but until then, please CC me on all
> Time::Object related messages]
>
>
> On Wed, 2 Aug 2000 08:14:22 +0100 (BST), Matt Sergeant wrote:
>
> >I used to be a C programmer myself (well OK, I was a C++ programmer...),
> >but I'd rat
Bennett Todd wrote:
>
> (Migrated from bootstrap)
>
> 2000-07-24-10:17:54 Dan Sugalski:
> > Perl 6 will most *definitely* be an embedded perl. Easy and clean
> > embedding is one of my primary goals. A small core with extended
> > functionality provided by non-core things is a secondary one. (An
Tom Christiansen wrote:
>
> >sub mapf(&;\@\@\@\@\@\@\@\@\@) {
>
> Steal from lisp:
>
> map
> maap
> maaap
> mapp
> mappp
> maappp
> ...
Should be feasible with an AUTOLOAD that takes a certain kind of regular
expression...
sub AUTOLOAD /^ma+p+$/ {
}
Some for the '
Dan Sugalski wrote:
>
>
> I'd also like to see lexicals addressed by name through some sort of symbol
> table-ish thing. Maybe:
>
>$PAD{my_var}[-1]
>
> would give a ref to the lexical my_var that exists one level of scope out
> from the current, or at least the my_var that's masked by the
30 matches
Mail list logo
