On Wed, 02 Aug 2000 20:58:51 -0700, Nathan Wiger wrote:
>=head1 IMPLEMENTATION
>
>The open() and opendir() functions would have to be altered to take one
>argument (not two) and return the corresponding file object or undef.
Actually, open() currently CAN have just one parameter. What it does, i
Glad to see the tide of sentiment towards making strictness the default
:-) To feed my personal fetish for optional site policies prohibiting
disabling certain strictness, can anyone enumerate circumstances when you
*cannot* currently achieve something desirable under one of the
strictnesses?
On 02 Aug 2000 16:42:35 -0700, Randal L. Schwartz wrote:
>Steve> We could add a 'then' keyword.
>
>We have one. It's called "comma in a scalar context". :)
Now do the same with a print command.
Aren't you trying to hard leaning backwards?
--
Bart.
Job Description
Perl 6 Language Individual Contributor
Nathan Wiger <[EMAIL PROTECTED]>
The goal of my position is not to really do any one thing, but rather to
try and contribute ideas and, when possible, actual code across a broad
range of topics. This includes writing RFCs, leading discussion
Jonathan Scott Duff writes:
> > In the future, if you want to submit an RFC mail it to
> > [EMAIL PROTECTED] only.
>
> http://tmtowtdi.perl.org/rfc/meta/ says that you should send your RFCs to
> [EMAIL PROTECTED] rather than [EMAIL PROTECTED]
They go to the same place. However, I meant to onl
subscribe information and more at: http://tmtowtdi.perl.org/
List name: perl6-language-mlc
Chair: Michael J. Mathews <[EMAIL PROTECTED]>
Charter:Discuss and redraft the multiline comments RFC
Timescale: 1 week (end Thursday 10th August)
Deliverables: Michael to post
Tim Bunce said:
> On Wed, Aug 02, 2000 at 10:57:27AM -0700, Larry Wall wrote:
> > <...>
> > That's a good summary of what we've been thinking. Here's another
> > article that talks about a lot of the things we *should* be thinking.
> > In fact, it's possible this article should be required readin
On Wed, 2 Aug 2000, Jonathan Scott Duff wrote:
> On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > > Deprecate localtime() and replace with
> >
> > I'm willing to take a first whack at this one (but only with lots of
> > input from others).
>
> I'll help. Let's call the re
Please don't reply to this one or threadlists will be screwed up! Reply
to the second (auto-generated) one later in the perl6-language mailbox.
(Hit the button a second before Nat's email! Oh, well...)
Nathan Wiger wrote:
>
> =head1 TITLE
>
> Modify open() and opendir() to return filehandle ob
On Wed, Aug 02, 2000 at 10:09:04PM -0600, Nathan Torkington wrote:
> I'm about to push the button that will send my private set of RFCs
> off to the archive and mail them to perl6-announce. Fingers crossed.
Hooray!!
> If I've forgotten your RFC, please send it to [EMAIL PROTECTED]
>
> In the f
=head1 TITLE
Modify open() and opendir() to return handle objects
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 2 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 14
=head1 ABSTRACT
Currently, open() and opendir() are given handle arguments, whose valu
=head1 TITLE
Highlander Variable Types
=head1 VERSION
Maintainer: Andy Wardley <[EMAIL PROTECTED]>
Date: 01 Aug 2000
Version: 1.0
Mailing List: [EMAIL PROTECTED]
Number: 9
=head1 ABSTRACT
Perl5 supports three distinct variable types for any given variable
name correspondin
=head1 TITLE
Filehandles should use C<*> as a type prefix if typeglobs are eliminated.
=head1 VERSION
Maintainer: Peter Scott <[EMAIL PROTECTED]>
Date: 2 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 10
=head1 ABSTRACT
The lack of a type-defining punctuation chara
=head1 TITLE
Lexical variables made default
=head1 VERSION
Maintainer: J. David Blackstone <[EMAIL PROTECTED]>
Date: 1 August 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 6
=head1 ABSTRACT
Prior to version 5, all implementations of Perl were designed with
only dynamic variable
=head1 TITLE
Higher resolution time values
=head1 VERSION
Maintainer: Gisle Aas <[EMAIL PROTECTED]>
Date: 2000-08-02
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 7
=head1 ABSTRACT
All functions that return time values (seconds since epoch) should use
floating point numbers to
=head1 TITLE
type inference
=head1 VERSION
Maintainer: Steve Fink <[EMAIL PROTECTED]>
Date: 1 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 4
=head1 ABSTRACT
Types should be inferred whenever possible, and optional type qualifiers
may be used to gain whatever level of
=head1 TITLE
The AUTOLOAD subroutine should be able to decline a request
=head1 VERSION
Maintainer: Leon Brocard <[EMAIL PROTECTED]>
Date: 02 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 8
=head1 ABSTRACT
In Perl 5, the first AUTOLOAD subroutine found in an object's h
=head1 TITLE
variable usage warnings
=head1 VERSION
Maintainer: Steve Fink <[EMAIL PROTECTED]> for now
Date: 2 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 12
=head1 ABSTRACT
"VARIABLE used only once: possible typo" should be replaced with
warnings on uses of uninitia
=head1 TITLE
messages.rfc - An RFC to discussing the wisdom of allowing run time error
and warning messages to be modified at run time
=head1 VERSION
Maintainer: Corwin Brust <[EMAIL PROTECTED]>
Date: 1 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 3
=head1 AB
=head1 TITLE
Request For New Pragma: Implicit
=head1 VERSION
Maintainer: Bryan C. Warnock <[EMAIL PROTECTED]>
Date: 01 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 2
=head1 ABSTRACT
Perl 6 should add a new pragma called C.
=head1 DESCRIPTION
I am lazy. I
I'm about to push the button that will send my private set of RFCs
off to the archive and mail them to perl6-announce. Fingers crossed.
The RFC archive is at http://tmtowtdi.perl.org/rfc/
If I've screwed up your RFC, please let me know.
If I've forgotten your RFC, please send it to [EMAIL PROT
=head1 TITLE
Modify open() and opendir() to return filehandle objects
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 2 Aug 2000
Version: 1.0
Mailing-List: perl6-language
=head1 ABSTRACT
Currently, open() and opendir() are given handle arguments, whose values
are twiddled if
On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > Deprecate localtime() and replace with
>
> I'm willing to take a first whack at this one (but only with lots of
> input from others).
I'll help. Let's call the replacement gmt2date() for now.
gmt2date() should at least (IMH
On Wed, 2 Aug 2000, Nathan Wiger wrote:
> Tom Christiansen wrote:
> >
> > >Not sure I agree with that. I think one point of confusion / perceived
> > >difference between filehandles, open(), and basically every other
> > >builtin is that all the others *return* what you want.
> >
> > tie and b
> Yes, but then each of those has to be explained specially. People
> *expect* assignment to "autovivify", as it were. But open() et al
> are essentially a 3rd syntax for constructors, and that's about one
> syntax too many, give or take a few.
I agree with this. I think of open() a lot more li
Steve Simmons writes:
: On Tue, Aug 01, 2000 at 04:47:47PM -0400, Dan Sugalski wrote:
:
: > Put together an RFC for it. (Soon!) This is a language topic, but it will
: > impact internals a touch, and I'd like to get as many of the "impact
: > internals" things spec'd out as soon as possible . .
Tom Christiansen wrote:
>
> >Not sure I agree with that. I think one point of confusion / perceived
> >difference between filehandles, open(), and basically every other
> >builtin is that all the others *return* what you want.
>
> tie and bless and chop and chomp also all act upon their argumen
Tom Christiansen writes:
: >Not sure I agree with that. I think one point of confusion / perceived
: >difference between filehandles, open(), and basically every other
: >builtin is that all the others *return* what you want.
:
: Think of all the {file,dir}handle syscalls. They don't do that.
>Not sure I agree with that. I think one point of confusion / perceived
>difference between filehandles, open(), and basically every other
>builtin is that all the others *return* what you want.
tie and bless and chop and chomp also all act upon their argument(s).
Just to name a few. bless ha
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
>> I've just asked for a multiline comment sublist to be set up. Do any
>> of the rest of these RFCs want/need a sublist?
TC> What is the purpose of ghettoizing everying cohering topic? Making
TC> us subscribe to infinite list
>Not sure I agree with that. I think one point of confusion / perceived
>difference between filehandles, open(), and basically every other
>builtin is that all the others *return* what you want.
Think of all the {file,dir}handle syscalls. They don't do that.
They autoviv an object.
--tom
>Russ talked about doing that. I think it would have to be called
>nntp.perl.org.
I can trivially repoint the old news.perl.com to wherever works best.
--tom
Tom Christiansen wrote:
>
> >Except that you can test for failure by checking to see if $fh is defined.
>
> Let your true be true and your false be false.
>
> open($fh, "<", $filename) || die;
>
> --tom
Not sure I agree with that. I think one point of confusion / perceived
difference betw
On Thu, 3 Aug 2000, Simon Cozens wrote:
> > Is there an open NNTP server running with all these as the perl.*
> > groups? That would help a lot.
>
> It would, yes. I've been toying with the idea of setting one up, but
> I think it should be news.perl.org
Russ talked about doing that. I think i
OK, I'm now up to date on perl6-language. Ugh.
Here's the RFC list as it currently stands. I'll keep reposting this
every few days as it changes. I'll also put it up at:
http://infotrope.net/opensource/software/perl6/
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
At 10:27 PM 8/2/00, Tom Christiansen wrote:
> >What extra could reasonably have been done?
>
>Should one really have to find the the time to read each of *hundreds*
>of messages each and every day in order to keep up with this stuff?
>Or should one be held accountable to for eyes glazing over admi
> Um, what stops open returning undef on failure (and setting $!), so I could do
>
> $fh = open $filename or die "open $filename failed: $!\n";
Exactly. You don't lose anything because open() will still return "true"
(a handle) or "false" (undef).
-Nate
On Wed, Aug 02, 2000 at 08:11:36PM -0600, Tom Christiansen wrote:
>
>That seems like a *really* bad idea, since anyone who misses the
>creation doesn't get to play, nor does someone who changes their
>mind later. Well, not easily.
>
>That every topic should have its own list is a pain in the ass.
>Great insight, thanks. It's obvious that I'll have to do a lot more
>research before (possibly) resubmitting anything on this subject. I do
>like the idea of at least being able to fiddle with input source
>tainting (since this is what usually gets me, even if I know the input
>source is safe). D
Larry-
Great insight, thanks. It's obvious that I'll have to do a lot more
research before (possibly) resubmitting anything on this subject. I do
like the idea of at least being able to fiddle with input source
tainting (since this is what usually gets me, even if I know the input
source is safe)
On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > That Perl should stay Perl
>
> Do we need an RFC for this? Seems like this is more of a "guiding
> concept" that should be intergrated into everything. Just my opinion.
Then we need to enshrine it. I'll cook something up soon.
--
> Reimplement Warnings and Tainting as Pragmas
> Nathan Wiger <[EMAIL PROTECTED]>
You can delete this one. 'use warnings' is already in 5.6 (sorry!) and
tainting looks near-impossible (thanks Larry for the insight!). I might
(after tons of research) resubmit something on tainting, but for
On Wed, Aug 02, 2000 at 08:27:19PM -0600, Tom Christiansen wrote:
> Should one really have to find the the time to read each of *hundreds*
> of messages each and every day in order to keep up with this stuff?
Nope. That's why you can select which lists you want to join.
I think you're trying to h
On Wed, 02 Aug 2000, Chaim Frenkel wrote:
> (Walks away shaking head, in wonder and amazement.)
Hey, it took me two weeks to hack the parser into doing this
at work. (Well, to some extent. It isn't module friendly.)
But you may as well kill-file me now, 'cause there are sure to be more.
My Pe
On Wed, Aug 02, 2000 at 11:57:21AM -0400, John Porter wrote:
>Tom Christiansen wrote:
>> >I feel strongly that "my" and "our" should both be renamed,
>> >as well as "local".
>>
>> What then do you propose? my() and our() were chosen for their brevity.
>
>Well, "var" is pretty short. And perhaps
Thus it was written in the epistle of Tom Christiansen,
>
> >Could you please write up an RFC on this?
>
> When in the process are we supposed to argue against this?
After the RFC is written, I believe. By analogy to typical committee action
(yes, I expect that we've all got a good quote re: c
>What extra could reasonably have been done?
Should one really have to find the the time to read each of *hundreds*
of messages each and every day in order to keep up with this stuff?
Or should one be held accountable to for eyes glazing over adminstrative
metadiscussions (a crack into which for
> Thanks for the advice. Would "production" have been less likely to offend
>than "real-world"?
Perhaps. Or "conservative". Or "cautious". Or "paranoid". :-)
--tom
Thus it was written in the epistle of Tom Christiansen,
> >Doesn't print 'GLOB' for me, but that's because a lot of real-world systems
> ^^
> >haven't hit 5.6.0 (I'm guessing, not absolutely sure that's the cause),
>
> If you look at
On Wed, Aug 02, 2000 at 08:00:57PM -0600, Tom Christiansen wrote:
> >Doesn't print 'GLOB' for me, but that's because a lot of real-world systems
> ^^
> >haven't hit 5.6.0 (I'm guessing, not absolutely sure that's the cause),
> If you
On Wed, 2 Aug 2000, Tom Christiansen wrote:
> >Tom Christiansen writes:
> >> What is the purpose of ghettoizing everying cohering topic? Making
> >> us subscribe to infinite lists to wear us down?
>
> >Yes.
>
> >If you really care about the topic, you'll join the list. If you
> >don't care, s
On Wed, Aug 02, 2000 at 08:13:08PM -0600, Tom Christiansen wrote:
> >> Making us subscribe to infinite lists to wear us down?
> >You know about perl6-all, right?
> Nope, I didn't.
> Which is the very problem of which I was speaking.
> Secret cabals and all.
It was publicly announced, although the
On Wed, Aug 02, 2000 at 08:13:08PM -0600, Tom Christiansen wrote:
> >> Making us subscribe to infinite lists to wear us down?
> >You know about perl6-all, right?
>
> Which is the very problem of which I was speaking.
> Secret cabals and all.
So secret it was recorded on:
i) The perl6 metalis
>> Making us subscribe to infinite lists to wear us down?
>You know about perl6-all, right?
Nope, I didn't.
Which is the very problem of which I was speaking.
Secret cabals and all.
--tom
Tom Christiansen writes:
> That seems like a *really* bad idea, since anyone who misses the
> creation doesn't get to play, nor does someone who changes their
> mind later. Well, not easily.
>
> That every topic should have its own list is a pain in the ass.
It's an experiment. Time will tell
>Could you please write up an RFC on this?
>K.
>On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>>There was some discussion at TPC4 that typeglobs could be expunged from
>>P6. If this is likely, it would free up a type-defining punctuation
>>character (*).
>>
>>Could this be used
>Tom Christiansen writes:
>> What is the purpose of ghettoizing everying cohering topic? Making
>> us subscribe to infinite lists to wear us down?
>Yes.
>If you really care about the topic, you'll join the list. If you
>don't care, stay off the list and don't bother the happy workers.
>That's
On Wed, Aug 02, 2000 at 08:05:15PM -0600, Tom Christiansen wrote:
> >I've just asked for a multiline comment sublist to be set up. Do any
> >of the rest of these RFCs want/need a sublist?
>
> What is the purpose of ghettoizing everying cohering topic?
To get those people who actually care a
Tom Christiansen writes:
> What is the purpose of ghettoizing everying cohering topic? Making
> us subscribe to infinite lists to wear us down?
Yes.
If you really care about the topic, you'll join the list. If you
don't care, stay off the list and don't bother the happy workers.
That's the pla
Could you please write up an RFC on this?
K.
On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>There was some discussion at TPC4 that typeglobs could be expunged from
>P6. If this is likely, it would free up a type-defining punctuation
>character (*).
>
>Could this be used for fil
On Tue, Aug 01, 2000 at 09:18:12PM +, Nick Ing-Simmons wrote:
>We need a quick glossary:
>
>perl core:
> perl.exe + perl.dll or .../bin/perl + libperl.so
>
>perl distribution
> anything from perl6.tar.gz
>
>Optional module
> things in CPAN
I've used the following terms:
Perl 6
>I've just asked for a multiline comment sublist to be set up. Do any
>of the rest of these RFCs want/need a sublist?
What is the purpose of ghettoizing everying cohering topic? Making
us subscribe to infinite lists to wear us down?
--tom
Tom Christiansen wrote:
>
[snip]
> It's certainly a myth than "big projects" *can't* be developed
> without OO. Well, unless you consider an operating system, a
> programming language, or an editor to be small projects--and I for
> one do not. OO can help, sure, but not a trifle as much as can
On Tue, Aug 01, 2000 at 01:09:46PM -0800, Michael Fowler wrote:
>
>Several people have suggested strong typing as a feature, and have been shot
>down one by one. However, I think it can be done without forcing it on
>everyone.
>
>In fact, it can be done with Perl 5, as various people have pointed
>Doesn't print 'GLOB' for me, but that's because a lot of real-world systems
^^
>haven't hit 5.6.0 (I'm guessing, not absolutely sure that's the cause),
If you look at it, you'll notice that "real" is here being used as
something o
On Wed, Aug 02, 2000 at 01:23:35PM +0100, Graham Barr wrote:
>
>I really should get all these ideas into an RFC.
Yes, please :)
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
P
> Formats out of core
> Switch statement
>
> Anyone want to put their name next to them?
Me.
Damian
> Let me reiterate my view of pragmas. They can warp the language any
> way you please, as long as they don't impact other modules. I wouldn't
> even mind if someone wrote a pragma that lets you program Perl in Latin.
Now you're just being silly!
;-)
Damianus
>Except that you can test for failure by checking to see if $fh is defined.
Let your true be true and your false be false.
open($fh, "<", $filename) || die;
--tom
Here are the language RFCs I'm aware of:
Multiline comments
Michael J. Mathews <[EMAIL PROTECTED]>
Lexical scoping by default
J. David Blackstone <[EMAIL PROTECTED]>
Higher resolution time valuse
Gisle Aas <[EMAIL PROTECTED]>
AUTOLOAD declining
Leon Brocard <[EMAI
> In perl5,
>
> /(??{ $FOO })/
>
> delays the interpolation of $FOO, so as to be able to have
> recursively defined regexps.
Of course, that example might in itself be sufficient reason
to completely redesign the regex syntax!
Damian
PS: I'll probably have a RFC on that i
Yes indeed:
List name: perl6-language-mlc
Chair: Michael J. Mathews <[EMAIL PROTECTED]>
Charter:Discuss and redraft the multiline comments RFC
Timescale: 1 week (end Thursday 10th August)
Deliverables: Michael to post the redrafted RFC back to perl6-language
Ask, can
At 10:36 AM 8/3/00 +0900, Simon Cozens wrote:
>On Wed, Aug 02, 2000 at 04:26:56PM -0700, Nathan Wiger wrote:
> > I tend to agree with Tom's argument here. open() is kind of funny
> > anyways. Why couldn't it work like this, similar to FileHandle:
> >
> >$fh = open $filename;
>
>Testing for fai
On Thu, 3 Aug 2000, Simon Cozens wrote:
> On Wed, Aug 02, 2000 at 04:26:56PM -0700, Nathan Wiger wrote:
> > I tend to agree with Tom's argument here. open() is kind of funny
> > anyways. Why couldn't it work like this, similar to FileHandle:
> >
> >$fh = open $filename;
>
> Testing for fail
> >Also read Damien Conway's "Object Oriented Perl" if you want to go further.
>
> Unlike the famous title by Hesse, in this case that would be spelled
> DamiAn, actually. :-)
Yes, I'm named after a leper, not the AntiChrist ;-)
> I think I can with safely predict that sixth
On Wed, Aug 02, 2000 at 04:26:56PM -0700, Nathan Wiger wrote:
> I tend to agree with Tom's argument here. open() is kind of funny
> anyways. Why couldn't it work like this, similar to FileHandle:
>
>$fh = open $filename;
Testing for failure. It's a basic tenet that system calls can be
tested
Chaim Frenkel writes:
: No.
This sort of argument is not terrilby useful.
Really, I don't see any big problem with the notion of the values of void
expressions being sent somewhere, as long as it's lexically scoped, and
doesn't rely on a global default filehandle. This kind of default
output ha
> No: lists are the plural whatzitzes, containing zero or more singular
> whatzitzes. They are ordered. Arrays hold lists.
I tend to agree with Tom's argument here. open() is kind of funny
anyways. Why couldn't it work like this, similar to FileHandle:
$fh = open $filename;
print $fh "so
On Wed, Aug 02, 2000 at 06:28:47PM -0600, Tom Christiansen wrote:
> >I'd also like some 'what are you' introspection I can do on all scalars, on
> >a more formal basis than 'ref'. Either an expansion of the 'ref' functionality
> >to cover filehandles, or a more general system...
> What do you mean
Graham Barr writes:
: On Wed, Aug 02, 2000 at 11:50:10AM -0400, Sam Tregar wrote:
: > On 2 Aug 2000, Gisle Aas wrote:
: >
: > > =head1 PERL5 PORTABILITY
: > >
: > > Calls to time() could be transformed to int(time()) when converting
: > > perl5 programs to perl6.
: >
: > Unless there's a:
: >
Peter Scott writes:
: At 06:28 PM 8/2/00 -0600, Tom Christiansen wrote:
: >ref() has always been a de facto typeof operator, no?
: >
: > open my $fh, "< /etc/motd";
: > print ref $fh
: >GLOB
:
: Can we make that IO in P6...?
Maybe, but it might be some class derived from an IO object, de
At 06:28 PM 8/2/00 -0600, Tom Christiansen wrote:
>ref() has always been a de facto typeof operator, no?
>
> open my $fh, "< /etc/motd";
> print ref $fh
>GLOB
Can we make that IO in P6...?
--
Peter Scott
Pacific Systems Design Technologies
>I'd also like some 'what are you' introspection I can do on all scalars, on
>a more formal basis than 'ref'. Either an expansion of the 'ref' functionality
>to cover filehandles, or a more general system...
What do you mean, "formal"? ref() has always been a de facto typeof
operator, no?
o
>If the prefix-less form of filehandles was absent from Perl 6, I would be
>far less enthusiastic about my RFC. I agree; they're a kind of scalar.
>(Just occurred to me that one could view the % prefix of hashes as denoting
>a key-value pair by virtue of looking like two o's separated by a
>d
Peter Scott writes:
: If the prefix-less form of filehandles was absent from Perl 6, I would be
: far less enthusiastic about my RFC. I agree; they're a kind of scalar.
In fact, they're a kind of object.
: (Just occurred to me that one could view the % prefix of hashes as denoting
: a key-val
On Wed, Aug 02, 2000 at 02:51:20PM -0400, John Porter wrote:
> Peter Scott wrote:
> > Filehandles should use C<*> as a type prefix if typeglobs are eliminated.
> I missed previous discussion of this (if there was any),
> but it's an idea I've already thought about.
> It has my vote, fwiw.
I have
Nathan Wiger writes:
: Is there any interest to do this in the community with tainting? Adding
: a 'use tainting' to Perl 6 (or 5.7, for that matter)?
Unfortunately, tainting is a data-flow/data-typing concept, and when
you try to implement data-flow/data-typing concepts with lexical
scopes, you
If the prefix-less form of filehandles was absent from Perl 6, I would be
far less enthusiastic about my RFC. I agree; they're a kind of scalar.
(Just occurred to me that one could view the % prefix of hashes as denoting
a key-value pair by virtue of looking like two o's separated by a
divide
Thus it was written in the epistle of Tom Christiansen,
>
> What about regexes?
>
> $foo = qr/blech/;
>
> Should that be /foo instead? :-)
>
> Notice how even objects use $, not something else.
<*chuckle*> Ok, point conceded.
Ted
--
Ted Ashton ([EMAIL PROTECTED]), Info Sys, Southern
>Scalars, hashes, arrays. There's actually more than one type of plural here,
>gramatically:
>scalars hashes arrays
>singulardualplural
>(Or am I the only one left who did Ancient Greek? :)
Nope: pudge and larry, at least.
>> (and don't say, "because plural *means* more
>Perl 5 supports OO quite well.
Yup! Perl already supports classes and objects, single and multiple
inheritance, instance methods and class methods, access to overridden
methods, constructors and destructors, operator overloading, proxy
methods via autoloading, delegation, a rooted hierarchy for
> "Steve" == Steve Fink <[EMAIL PROTECTED]> writes:
Steve> We could add a 'then' keyword.
We have one. It's called "comma in a scalar context". :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[EMAIL PROTECTED]> http://www.stonehenge.com/merlyn/>
Perl/Uni
"Randal L. Schwartz" wrote:
>
> > "Martyn" == Martyn Pearce <[EMAIL PROTECTED]> writes:
>
> Martyn> Possibly, although I must ask: since everything is up-for-grabs, I ask
> Martyn> (without implying any feeling one-way-or-tother):
> Martyn> How useful is the , operator in it's C-style statem
On Wed, Aug 02, 2000 at 05:31:06PM -0400, Ted Ashton wrote:
> But that, precisely, was my point: Arrays *and* hashes.
Scalars, hashes, arrays. There's actually more than one type of plural here,
gramatically:
scalars hashes arrays
singulardualplural
(Or am I the only one l
On Wed, Aug 02, 2000 at 04:32:40PM +0100, Andy Wardley wrote:
> This would permit the rationalisation and simplification of the syntax
> required to access individual elements or slices of arrays and hash arrays,
> while remaining backwardly compatible with Perl5 syntax.
This is the rationale? So
wei ye wrote:
> I'm interested in how OO Perl 6 will be.
> It's very hard to develop big project in a language without OO support,
> so I think OO should be a very important part of Perl6.
Perl 5 supports OO quite well. Read the docs by typing 'perldoc '
where is one of:
perlboot
>> No: lists are the plural whatzitzes, containing zero or more singular
>> whatzitzes. They are ordered. Arrays hold lists.
>I tend to agree with Tom's argument here. open() is kind of funny
>anyways. Why couldn't it work like this, similar to FileHandle:
> $fh = open $filename;
> print $
On Wed, Aug 02, 2000 at 01:48:36PM -0600, Tom Christiansen wrote:
> >Isn't this covered by locales?
> Unicode and locales are immiscible.
In Perl 5. This is *by no means* a general statement.
ICU is, for instance, a Unicode locale library.
--
Gosh that takes me back... or is it forward? That's
I thought that that was just the plan.
Form sub lists to collect ideas that needed hashing, if that hashing got
involved make sub-lists to reach consensus on those.
You have a nice thread handeling mail client, don-ch tom?
-Corwin
-Original Message-
From: Tom Christiansen [mailto:[EMA
On Wed, Aug 02, 2000 at 12:22:10PM -0400, John Porter wrote:
> sub interleave(\@;\@\@\@\@\@\@\@\@) {
...
> }
>
> sub mapf(&;\@\@\@\@\@\@\@\@\@) {
...
> }
>
>
> I guess my question is, why do these need to be builtins?
sub push (\@@) { @{$_[0]} = (@{$_[0]}, @_[1..@_]); }
--
Just imagine
1 - 100 of 294 matches
Mail list logo
