Re: PERL6STORM - tchrist's brainstorm list for perl6

2000-09-21 Thread Charles Lane
Tom Christiansen <[EMAIL PROTECTED]> wrote: >=item perl6storm #0016 > >object as scope/namespace? see python. it's danged clean >there in that you can now implement safe trivially. >don't have to keep inventing crazy overloads. > Yes, this would be great! >=item perl6storm #0025 > >Make -T t

Re: assign to magic name-of-function variable instead of "return"

2001-02-02 Thread Charles Lane
Peter Scott <[EMAIL PROTECTED]> wrote: >At 07:12 PM 2/1/01 -0600, David L. Nicol wrote: >>I recalled hearing about a language (was it java?) where >>you set the return value of a function (was it VB?) by >>assigning to the name of the function within the function body, >>so the last line would be

Re: System epochs

2000-09-12 Thread Charles Lane
Nathan Wiger <[EMAIL PROTECTED]> wrote: > I'm writing a prototype for RFC 99, Standardize ALL Perl platforms on > UNIX epoch, which does some simplistic manipulation of CORE::time to > return the UNIX epoch on all platforms. > > My question is: Are there any system-specific epochs that Perl uses >

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-14 Thread Charles Lane
Chaim Frenkel <[EMAIL PROTECTED]> writes: > "AD" == Andy Dougherty <[EMAIL PROTECTED]> writes: >AD> In my humble opinion, I think perl's time() ought to just call the C >AD> library's time() function and not waste time mucking with the return >AD> value. Instead, if the time is to be stored e

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-14 Thread Charles Lane
Andy Dougherty <[EMAIL PROTECTED]> writes: On Thu, 14 Sep 2000, Charles Lane wrote: >> On at least some non-Unix systems, the time() function is itself an attempt >> to emulate Posix functionality...note that I say "attempt". And also note > >Do you mean th

RE: Hopefully last draft of AL

2000-09-22 Thread Charles Lane
Dan Sugalski <[EMAIL PROTECTED]> wrote: >At 02:29 PM 9/22/00 -0500, Garrett Goebel wrote: > >>Can't a trademark be used to protect "Perl", even if the code is in the >>public domain? > >Dunno. Probably, but I'm not a lawyer, and that might be taking things to >places we'd rather not go. IANAL eit