On Tue, Aug 08, 2000 at 10:47:10PM -0700, Russ Allbery wrote:
> John Tobey <[EMAIL PROTECTED]> writes:
> > On Wed, Aug 09, 2000 at 02:22:22AM +0200, Bart Lateur wrote:
>
> >> date() would be more general, and replace both. You can pass it a time
> >> zone,
On Wed, Aug 09, 2000 at 02:22:22AM +0200, Bart Lateur wrote:
> I have a server in the UK, while I'm in Belgium. Different time zones.
> So localtime() won't return the time in *my* localtime.
>
> So we have two almost identical functions in the core, gmtime and
> localtime, where one gives an off
On Mon, Aug 07, 2000 at 01:44:28AM -0500, Jonathan Scott Duff wrote:
> On Sun, Aug 06, 2000 at 11:07:02AM -0700, Russ Allbery wrote:
> > Basically, you don't want to go anywhere near this mess; it eats people.
>
> I agree.
>
> > I see two reasonable options to go with instead. One is to just us
On Sun, Aug 06, 2000 at 01:41:06PM -, Perl6 RFC Librarian wrote:
>$scalar = date; # scalar ctime date, same as current
>@array = date; # array of date/time values (new order)
>%hash= date; # hash of date/time values (new)
>$object = date; # object wi
Ken Fox <[EMAIL PROTECTED]> wrote:
> John Tobey wrote:
> > The Perl 5 (and older) behavior may preclude some optimizations.
>
> I can't think of any optimizations @_ assignment precludes.
> If we don't analyze dataflow to figure out if a sub modifies its
&
otyped subs are affected. my_sysread()
just needs a prototype, and it can work just like sysread().
--
John Tobey, late nite hacker <[EMAIL PROTECTED]>
\\\ ///
]]] With enough bugs, all eyes are shallow. [[[
/// \\\
This is not quite finished yet, as I read the rest of the C-- garbage
collection paper.
-John
=head1 TITLE
Elements of @_ should be read-only
=head1 VERSION
Maintainer: John Tobey <[EMAIL PROTECTED]>
Date: 3 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number:
eady. If this change is adopted, I
would make it conditional on C<$0 ne "-e"> so as not to disturb my
one-liners. (which are about 99% of the Perl programs I write...)
--
John Tobey, late nite hacker <[EMAIL PROTECTED]>
\\\
data-tracking mechanism aside from
security. If the keyword 'untaint' had to appear, it would be easier
to find security issues than when m/(.*)/ is used.
Uh-oh, now we're getting back into perl6-language territory...
a
