* Simon Cozens <[EMAIL PROTECTED]> [06/14/2001 15:16]:
>
> OK, I've been teasing people about this for weeks, and it's time to stop.
> This is the current state of the Perl 6 emulator; it applies most things
> that Damian talked about in his keynote yesterday, and most of the things
> I've picked
> Another note: your examples with:
>
> local ($^T) = 0;
> $ENV{PATH} = read_config_file();
> local ($^T) = 1;
>
> is only using local() to confuse; it should be written with a block,
> correctly restoring the old value of $^T.
Sorry about that - I contemplated taking it
> Probably not with tie, but with function calls in general, sure. We can do
> some flow control analysis on the subs and propagate it outwards so we
> might know, for example, that:
>
>sub foo {
> my (@vars) = @_;
> return scalar @vars;
>}
>
> doesn't change its args or any gl
> I like this, but I'd like to see this, inter-thread queues, and events all
> use the same communication method. Overload filehandles to pass events
> around instead, so:
>
>my $thing = <$handle>;
>
> could read a record from a file, or get an event from the event queue, or
> receive some d
ainting via the $^T variable
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 31 July 2000
Version: 1
Mailing List: perl6-internals
Number: 1
=head1 Abstract
Currently, Perl requires that tainting be invoked along with the Perl
interpreter, via the -T switch. It would be n
> Several people have requested strong typing as a feature, but have been shot
> down with reasons such as "it's un-Perl-like", with an added "it'll slow
> everything down for those who don't want it".
Definitely.
> Unfortunately, accessing and manipulating tied variables is incredibly slow,
> s
> I think it's far from trivial, especially if you want to take into
> account network names, file versions, protection attributes and ACLs, ...
Sure, this all depends on what we're going to do with this data and at
what level. The biggest problem that modules like CGI.pm have to deal
with is jus
> And how do we make it easy to pass in a name to open?
In an email I sent to Jarkko off-list, I suggested this:
If we embedded full URI support into Perl, then people could write
portable scripts using URIs, or non-portable ones using native syntax.
*Internally*, both could be converted into so
> > I'm not sure anyone does that much in the way of time/date work that it'd
> > make a difference. Besides, we're talking internal here--time() may still
> > return Unix epoch seconds for compatibility reasons.
>
> Blah! I saw the prosal for an mjdate() routine and thought it was at
> the lang
> As for single datum access, I C[index]> or
> C{key}> should be considered. This however, is not the
> core of this proposal. Merely a possibility. Just as extending the
> inelegant metaphor above to C<{function()}->{key}> would become a
> possibility.
Personally, I think lists should always sta
> We need to get a new keyword for defining such a variable, I think
> "transaction" is too long, we could use "safe" for this reason.
The proposal looks good. But isn't this more a language issue at this
point? Seems like we'll have to figure out the behavior we want first.
Also, "safe" i
> Anyway, it doesn't matter; it's a lot more widely used than any other
> epoch, and epochs are completely arbitrary anyway. What's wrong with it?
I think the "What's wrong with it?" part is the wrong approach to this
discussion. Personally, I'm a 100% UNIX head. All I work on is UNIX
(thank hea
Larry Wall wrote:
>
> Oh, gee, where's your sense of history? (As in creating our own. :-)
> Maybe we should invent our own epoch, like the year 2000. Or use a
> really standard one, like the year 0 AD (aka 1 BC).
I don't know about this. Sounds cool, but I think we should stick to
something t
Jarkko Hietaniemi wrote:
>
> > Is Perl currently using different epochs on different platforms? If so, I
>
> Yes. MacOS and VMS. (Though VMS' localtime() uses the UNIX definition,
> just to be portable.) MacOS' epoch zero is 1900 (or was it 1901?),
> VMS' epoch zero is 17-NOV-1858 00:00:00.0
[cc'ed on internals as FYI]
> =item 36 (v1): Structured Internal Representation of Filenames
I think this should be discussed a good amount. I think URIs are cool,
but too much trouble for simple stuff. I don't want to have to write
"file:///etc/motd" everytime I want to address a file. Too cumb
> print "what's that, $perl?";
>
> Use of uninitialized value in concatenation (.) at -e line 1.
> This is misleading and confuses users. When Perl needs to report
> errors or warnings, it should describe the code the programmer wrote,
> regardless of how that's been translated within Perl.
Jonathan Scott Duff wrote:
>
>> standard like 0 AD isn't bad.
>
> Standard for whom? I bet there are *millions* of Jews for whom "0 AD"
> is meaningless. s/Jews/ calendar that predates christianity>/
Good point.
Unix epoch it is! :-)
-Nate
> C should be renamed to C for Perl 6, and
Heh. I'm working on an integrated tie proposal right now that uses this
exact notion - and even a C naming scheme! I guess I'll be
referencing your RFC... ;-)
-Nate
Simon Cozens wrote:
>
> On Fri, Sep 29, 2000 at 09:47:51PM -, Perl6 RFC Librarian wrote:
> > I am a fan of Perl and like what I see of the core C# _language_.
> > What I propose is to move Perl in the C# direction.
>
> So, this is the comedy RFC, eh?
Indeed.
Since you quoted a couple of m
Dan Sugalski wrote:
>
> Alice in Wonderland is, of course, the quintessential CS text. It never
> hurts to keep in mind that everything you know could well be wrong. :)
Another one I'd like to suggest, which I suspect (hope?) most everyone
has already read:
The Hitchhiker's Guide to the Galax
Simon Cozens wrote:
>
> =head2 Implementation Language
>
> C++ gives us OO and headaches, is wildly non-portable due to a lack of
> decent implementations, and we don't have enough experience of it. C's
> portable and everyone knows it, but it's a swine for doing OO things.
Don't forget we can
Simon Cozens wrote:
>
> Oh boy, it's OO syntax nargery time again. *sigh*.
> > I think it would be cool
>
> Good for you. This is internals design; perl6-language is over there --->
> and the "ph33r mY |<" phase is supposed to be over now
> anyway.
Cool! Thanks alot for the useful feedback. Co
First off, this looks really cool to me, nice job. The only thing I'm a
little surprised by is this:
> =head2 Independent subsystems
>
> Perl also has a number of subsystems that are independent of any
> single module.
>
> =item PerlIO subsystem
>
> =item Regex engine
I would have actually ex
Jarkko Hietaniemi wrote:
>
> > // numeric comparisons
> > int (*NUMCMP) (SVAL *this, SVAL *value);
> > int (*NUMEQ) (SVAL *this, SVAL *value);
> > int (*NUMNE) (SVAL *this, SVAL *value);
> > int (*NUMLT) (SVAL *this, SVAL *value);
> >
24 matches
Mail list logo
