Re: TIL redux (was Re: What will the Perl6 code name be?)

2000-10-26 Thread Chaim Frenkel
ops. Were Perl5 used the C inner loop, the TIL could have a tighter asm loop, or even direct machine calls. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Accessing perl's command line switches

2000-09-29 Thread Chaim Frenkel
that could reload itself, but without the -S and -I commands the runtime environment is not fully reflected. And if running under -T the enviornment is not trusted.) Is there something there already? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL

Re: RFC 85 (v2) All perl generated errors should have a unique identifier

2000-09-21 Thread Chaim Frenkel
ng is an enabler. I've seen code that actually looks at the value of $@ eval { ... } $@ !~ //; Why not make it simpler eval { } $@ !~ any( ); # Damian's Superpositions.

Re: RFC 85 (v2) All perl generated errors should have a unique identifier

2000-09-20 Thread Chaim Frenkel
string, locks away any possiblities of adjusting the text of the message or even making the error string localizable. Consider allowing perl to emit error messages in French, Latin, or Klingon without breaking the code. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 85 (v2) All perl generated errors should have a unique identifier

2000-09-20 Thread Chaim Frenkel
is. Issuing a unique error id for non-core modules will be a nightmare. And I don't think we want to start up a IANA. The $@->facility, $@->id pair could be considered unique for non-core errors. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-18 Thread Chaim Frenkel
yles having tristate logic and NULL propogation would make some programming task a bit more straightforward. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: pack/unpack is damn unperlish. Explain them as Perl.

2000-09-18 Thread Chaim Frenkel
that perl can use it correctly. binary integers stay integers if they are in the wrong endiness the bits get flipped properly. un so weiter. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 230 (v1) Replace C built-in with pragmatically-induced C function

2000-09-18 Thread Chaim Frenkel
7;t want to do the monitoring, then some hook that is called just after the header or before the first line, and just after the last or before the footer. I must of missed it but what is the mechanism to force a page break? And is there a way of keeping a format emission either together or to al

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-17 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: NT> Chaim Frenkel writes: >> I would like to have an undef returned. NT> Ah, I see. You want subroutines to return undef if they're given it NT> for any of their arguments. That&

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-17 Thread Chaim Frenkel
s a good GL> expenditure of the fast CPUs of today, as a tradeoff towards GL> reliable processing. And maybe in Perl6 exception handling could GL> be less expensive than it is (by comparison to error codes) in GL> other languages? That's a quest

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-17 Thread Chaim Frenkel
empty list. Adding all these exceptions for non-exceptional and quite common scenerios is bothersome. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Multiple random number generators (was Re: RFC 208 (v2) crypt() default salt)

2000-09-17 Thread Chaim Frenkel
r generator, and return a reference to the generator allowing reseting or extraction of the next number via rand =item rand EXPR, RANDGEN_REF =item rand EXPR =item rand -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 229 (v1) Variable interpolation on demand.

2000-09-17 Thread Chaim Frenkel
n core. I thought he was asking for evaluating until nothing is left to interpolate. Something akin to: $x = eval "$x" while $x =~ /[$@]/; But more intelligent. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 230 (v1) Replace C built-in with pragmatically-induced C function

2000-09-17 Thread Chaim Frenkel
ariables? Point the format at which variable(s) to watch range => qw(name other) footer => "$From{name} - $To{name}"; Would it be worthwhile to have a quick and dirty way of having the formatter determine the max width and then allow the head

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-17 Thread Chaim Frenkel
27;@') would then be able to see the raw arguments. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-17 Thread Chaim Frenkel
>>>>> "JP" == John Porter <[EMAIL PROTECTED]> writes: JP> Chaim Frenkel wrote: >> >> Removing -1 as a valid result, could be a breakage (if someone is >> doing something weird with a negative result) JP> What, like using it as an index i

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-14 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: NT> Chaim Frenkel writes: >> Somehow I find >> if (40 == ($foo = substr($bar, index($bar, 'xyz' { >> } NT> I don't understand your hypothetical code. substr()

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-13 Thread Chaim Frenkel
(40 == substr($bar, $offset))) { } I use this style of safe failure when working in SQL. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 213 (v1) rindex and index should return undef on failure

2000-09-13 Thread Chaim Frenkel
$foo = "flabergasted"; substr($foo, index($foo, 'abc'), 20); # Returns undef If this is too much breakage what about only if it is the argument? $foo = "flabergasted"; $x = index($foo, 'abc'); substr($foo, $x, 20); # s

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-12 Thread Chaim Frenkel
the values will be done? Is this "@hash{@keys};" valid? Would it be possible to make push(%hash, @keys) work? Doesn't look likely is @keys the keys, the values, or both? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
t I need would be a win for me. Time for another missive in language design of why pop and push, shift and unshift are in, but union and intersection are not. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
f using the wrong data structure all TC> along -- that is, an array. But a Hash isn't the correct data structure either. It just has some, of the correct properties. Perhaps we should add a Set to the toolkit. Basically a hash with only the keys, no other baggage. But you still would argue ag

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
.) can be chucked all I would need is the key management part. Which could probably be boiled down to converting the hash key into a bit. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
pplication. Tiny minority? I'm no mathematician, but I've used set operations to avoid redoing known work. And I've used hashes simply because I have no other 'lazy' choice. But the code becomes harder to read. >From a conceptual level, when looking at the code (not t

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
h have to go through the same amount of work ("work is conserved") but one is more efficient in terms of the user's brainpower. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: $a in @b

2000-09-11 Thread Chaim Frenkel
>>>>> "AS" == Ariel Scolnicov <[EMAIL PROTECTED]> writes: AS> Chaim Frenkel <[EMAIL PROTECTED]> writes: >> yield EXPR - stop what I am doing now and give something else a >> a chance to do its things. And while you are doing >> that pl

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-11 Thread Chaim Frenkel
brace could be one of many things. Does the prototype help guide the decision that it is a block and not an anon-hash? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-11 Thread Chaim Frenkel
>>>>> "BL" == Bart Lateur <[EMAIL PROTECTED]> writes: BL> On 10 Sep 2000 00:33:43 -0400, Chaim Frenkel wrote: >> I view it as a mis-feature. BL> I'm sorry to disagree. But flattening of argument lists is one of those BL> things that make Perl,

-a and @F autospliting

2000-09-11 Thread Chaim Frenkel
a regex operation, one or the other wouldn't have to be populated.) Thoughts? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 195 (v1) Retire chop().

2000-09-11 Thread Chaim Frenkel
in general when doing line at a time filter processing. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-11 Thread Chaim Frenkel
ith my Set (@a, @b, @c);# Is the type distributive? @c = @a - @b; @c = @a + @b; @c = @a * @b; # cross product ? I'm not understaning your position. I could have used such an operation rather than rolling my own. And a module w

Re: $a in @b

2000-09-11 Thread Chaim Frenkel
e overloaded to work with lazy lists, continuations, and short-circuiting. yield EXPR - stop what I am doing now and give something else a a chance to do its things. And while you are doing that please take this EXPR from me. -- Chaim Frenkel

Re: $a in @b

2000-09-10 Thread Chaim Frenkel
accept the element it DC> was filtering: Why not spell it 'yield'? It seems to have all the right connotations. A sort of soft return. Gives of itself. Very polite. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: $a in @b

2000-09-10 Thread Chaim Frenkel
ested that a while ago, but Randal shot it down. Something about the block not being a loop, I think. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 114 (v2) Perl resource configuration

2000-09-10 Thread Chaim Frenkel
27; that can have itself configure. Yes, one could do it in the shell/program, but a simple 'standard' method might be worthwhile. use perlrc qw(:system :user); Though the range of options and settings are probably so vast that a single module capable of handling all scenerios would be so

Re: RFC 179 (v1) More functions from set theory to manipulate arrays

2000-09-10 Thread Chaim Frenkel
rect map than the twiddling with hashes. How are you drawing the line. Where does giving the user more power than a turing machine stop. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 52 (v2) List context return from filesystem functions

2000-09-09 Thread Chaim Frenkel
ere PerlLIO_chmod is defined as chmod on most righteous systems. So it PS> would be a matter of squirreling away the errno for each bad result. PS> I just can't get over the result in the successful case being an empty PS> list, though. And conversely. Maybe this isn't itching enough to be worth PS> scratching this hard, but it seemed like a good direction :-( Anyone got PS> any brilliant ideas before I withdraw it? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-09 Thread Chaim Frenkel
>>>>> "DC" == Damian Conway <[EMAIL PROTECTED]> writes: >> my_while { pred() } { # don't gimme no Tcl flac. >> ... >> } # no semicolon needed here! DC> Just added to the RFC :-) How would the parser handle this

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-09 Thread Chaim Frenkel
/merge/whatever is used. Or for ($x,$y,$z) ( (@x,@y,@z) ) an extra set of parenthesis could do the flattening. (only one list is 'visible' as the argument to the for. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 127 (v1) Sane resolution to large function returns

2000-09-05 Thread Chaim Frenkel
>>>>> "GL" == Glenn Linderman <[EMAIL PROTECTED]> writes: GL> Chaim Frenkel wrote: >> ($foo, $baz, @bar) = (1,(2,3),4) # $foo = 1 $baz=2, @bar=(3,4) >> >> Actually, looking at it like that makes it an ugly situation. The 'new' >&g

Re: functions that deal with hash should be more liberal

2000-09-04 Thread Chaim Frenkel
a LIST via @_. NT> The hash functions are prototyped as \%, meaning they are passed a NT> reference to the hash named as an argument. The reference-taking: NT> * permits them to change the data structures NT> * is faster (one value, not all the key/value pairs) What if keys wer

Re: Pre-RFC: Require a warning on spaces after here-document "terminator"

2000-08-29 Thread Chaim Frenkel
down. I can't remember the reason offered. (Speed?) I can see a possible issue print < -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Extended Regexs

2000-08-29 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: >> > * Using an array of "words" as an alternate list as part of a regex >> /match any of (${\join'|',@list}) here/ NT> $" = "|"; /@lis

Re: RFC 23 (v3) Higher order functions

2000-08-29 Thread Chaim Frenkel
ecause I *have* to ignore DC> them or my brain is going to melt. Unless I missed them. Did you leave pointers to the literature? Dan and the rest of the -internals folks will need them. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED]

Re: RFC 122 (v1) types and structures

2000-08-28 Thread Chaim Frenkel
a "type definition") of a block of memory, which PRL> is called a "struct." (rather than a "pseudohash" which is something PRL> that acts very similar but has a different internal representation.) PRL> Or we could use the C ke

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

2000-08-25 Thread Chaim Frenkel
or should we stand on our own two feet? Strange thought just crossed my mind. Would having a time object that is understood by perl be sufficient? It would smell and taste like an integer but would otherwise be magical. -- Chaim Frenkel

Something akin to ksh's <() and >() syntax

2000-08-25 Thread Chaim Frenkel
t;>) { (<{proc_arg1}, <{proc_arg2}) = split; } Damian, You have coroutines/generators out there. What about a data sink? Anything you have currently proposed that would do this neatly. -- Chaim FrenkelNonlin

Re: RFC 127 (v1) Sane resolution to large function returns

2000-08-24 Thread Chaim Frenkel
>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> At 02:25 PM 8/24/00 -0400, Chaim Frenkel wrote: >> But >> >> ($foo, $baz, @bar) = (1,(2,3),4) # $foo = 1 $baz=2, @bar=(3,4) >> >> Actually, looking at it like that makes

Re: RFC 127 (v1) Sane resolution to large function returns

2000-08-24 Thread Chaim Frenkel
ectation would be to have it become # $foo=1 $baz=2 @bar=(4) *blech*, I'm glad that you're doing the thinking. >>>>> "LW" == Larry Wall <[EMAIL PROTECTED]> writes: LW> Chaim Frenkel writes: LW> : LW> P.S. I thin

Re: RFC 127 (v1) Sane resolution to large function returns

2000-08-24 Thread Chaim Frenkel
ar return an object ref in scalar LW> context, as long as the object returned overloads itself to behave as LW> arrays and hashes currently do in scalar context. Isn't this an internals issue? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Make lvalue subs the default (was Re: RFC 107 (v1) lvalue subs should receive the rvalue as an argument)

2000-08-16 Thread Chaim Frenkel
s it great. You think there is a better _approach_ then tell the author. You are limited by what the author wrote. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 83 (v2) Make constants look like variables

2000-08-16 Thread Chaim Frenkel
tant-ness in my mind is an attribute or modifer of the value or perhaps of the container. It has no bearing on the scoping or type of the value. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 84 (v1) Replace => (stringifying comma) with =>

2000-08-16 Thread Chaim Frenkel
/I had arbitrary ranges for array indices. Hmm, I feel an RFC coming on my @arr :low(-32000) :high(+32000); my @population :low(1900) :high(2039); $population[1923] = 323000; How about my @population[1900:2039]; Looks funny though. -- Chaim Frenkel

Re: RFC 84 (v1) Replace => (stringifying comma) with =>

2000-08-16 Thread Chaim Frenkel
t Man", "they given you a number and takin' way your name. What was the name of the show? "Secret Agent"? And what came first the song or the show? What was the real theme song? The title song was never played during t

Re: RFC 111 (v1) Whitespace and Here Docs

2000-08-16 Thread Chaim Frenkel
ke the programer work. Are those tabs or spaces? And it doesn't strip the leading whitespace. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 82 (listops in list context)

2000-08-16 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: NT> Chaim Frenkel writes: >> [use wacky Unicode characters for new operators] >> I can see that this would give problems for current editors and displays, >> but by the time perl6 c

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

2000-08-16 Thread Chaim Frenkel
Perl <-> Perl cross system will break. Perl <-> other program same system will break. Pick your poison. I'd rather have cross system break. But if the epoch were available then an adjustment could be made intellegently.

Re: Default filehandles(was Re: command line option: $|++)

2000-08-16 Thread Chaim Frenkel
Thanks again. That's a bit strong. All we are doing is filtering the garbage for Larry. Larry may well be reading for flavour. And you forgot Rule #2. Larry can always change his mind. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Language WG report, August 16th 2000

2000-08-16 Thread Chaim Frenkel
rd. The containing WG would report the results upward. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 107 (v1) lvalue subs should receive the rvalue as an argument

2000-08-16 Thread Chaim Frenkel
>>>>> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes: CN> Can we please cut down on the traffic to perl-announce, maybe make it CN> moderated? Thanks, Perhaps, the esteemed Librarian could make the -announce a Bcc? -- Chaim Frenkel

Re: RFC 82 (listops in list context)

2000-08-16 Thread Chaim Frenkel
time perl6 comes out, perhaps the situation would be better. (Now, if we add all that APL symbols ...) Thoughts? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-08-16 Thread Chaim Frenkel
nd you, the instantaneous time is correct. But calculating backwards to what the instantaneous time would have been, or calculating what the instanataneous time will be will not work. But your blurb would be a lie. How would one ensure the correct difference to the TAI? And what would be the tr

Re: Default filehandles(was Re: command line option: $|++)

2000-08-16 Thread Chaim Frenkel
I.e. $STDOUT should always mean one and only one file at a time. Unless one wants to have a $DEFAULT filehandle and get rid of single arg select. >>>>> "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes: JSD> On Tue, Aug 15, 2000 at 06:53:30PM -0400, Chai

Re: RFC 104 (v1) Backtracking

2000-08-16 Thread Chaim Frenkel
>>>>> "MC" == Mark Cogan <[EMAIL PROTECTED]> writes: >> is equivalent to >> >> @a = (\$a, \$b, \$c); >> >> rather than what you wrote. MC> Ah, so it is. I'd argue that that's broken and should be handled with map MC&g

Re: RFC 104 (v1) Backtracking

2000-08-15 Thread Chaim Frenkel
MC> elements is an intuitive one, and having array iteration magically happen MC> when you're not looking is dangerous. Not unless you are coming from a math background or are an old basic programmer, and would like to have matrix operations built in. -- Chaim Frenkel

Re: RFC 107 (v1) lvalue subs should receive the rvalue as an argument

2000-08-15 Thread Chaim Frenkel
defined $newval; # rvalue context BB> # lvalue context BB> # verify new foo is in correct range BB> return $self{foo} if $$newval < $MINFOO; BB> return $self{foo} if $$newval > $MAXFOO; -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL

Re: command line option: $|++

2000-08-15 Thread Chaim Frenkel
will have to implement it anyway. The only other choice would be to start a -environment (or some such) list, but I don't think there will be that much traffic. Actually, it might be appropriate for horos(?) complaint list. (How's that coming along?) -- Chaim Frenkel

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

2000-08-15 Thread Chaim Frenkel
A> them" and by and large that works. It means your system clock drifts a RA> little over time and then gets corrected back by xntpd or something, but RA> in practice time on a Unix clock is monotonic. Hmm, that means, some seconds were really 2x as long as others. -- Chaim Frenke

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

2000-08-15 Thread Chaim Frenkel
ly short: BB> Into the future: to next December 31st or June 30th, whichever is BB> closer. BB> Into the past : to past January 1st or July 1st, whichever is BB> closer. Sorry, this makes no sense. BB> Leap-seconds are a PITA for generic time routines. Why?

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

2000-08-15 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: NT> Chaim Frenkel writes: >> Why? What is the gain? Perl only runs on the local machine. NT> Epoch seconds are a convenient representation for dates and times. NT> Varying epochs make it

Re: RFC 104 (v1) Backtracking

2000-08-15 Thread Chaim Frenkel
(@result = @a) or (@result = @b); >> >> That's what all my students keep expecting it to mean. MC> Seconded. MC> It seems obvious that @a should be the whole array @a, not an iteration MC> over its elements. If I want to iterate over @a, I should

Re: RFC 105 (v1) Downgrade or remove "In string @ must be \@" error

2000-08-15 Thread Chaim Frenkel
be uninitialized. I don't know if it is still true. But at one point in perl's life defined(@arr) was false before anything was assigned to the array. At this point this is highly frowned upon. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAI

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

2000-08-15 Thread Chaim Frenkel
to the UNIX PRL> epoch, while others use their own epochs (MacPerl uses 1904, for PRL> example). PRL> All versions of Perl on all platforms should maintain time both PRL> internally and externally as seconds since the UNIX epoch (00:00:00 01 PRL> Jan 1970 UTC). -- Chaim Frenkel

Re: Default filehandles(was Re: command line option: $|++)

2000-08-15 Thread Chaim Frenkel
zer for the corresponding per-filehandle value. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Default filehandles(was Re: command line option: $|++)

2000-08-15 Thread Chaim Frenkel
d also to STDOUT? select(OTHERFH); print "This goest to OTHERFH\n"; print STDOOUT "This went to STDOUT\n"; STDOUT is _not_ the default filehandle. It is the currently selected filehandle when perl starts. -- Chaim Frenkel

Re: RFC 99 (v1) Maintain internal time in Modified Julian (not epoch)

2000-08-15 Thread Chaim Frenkel
o distribute portable time and date calcuations, as part of the core, we will have to live with whatever the system libraries give us. (I don't want to think about Leap Seconds just yet.) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED]

Re: RFC 90 (v1) Builtins: zip() and unzip()

2000-08-14 Thread Chaim Frenkel
, isn't "reshape" the name of the APL operation? Hmm, reshape is its own inverse. I'll go for that as the name of the operation. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 99 (v1) Maintain internal time in Modified Julian (not epoch)

2000-08-14 Thread Chaim Frenkel
> including: PRL>1. The ability to do date arithmetic with simple math ops PRL>2. It can be used to easily derive many other sources, PRL> including UTC and local time PRL>3. It is platform and even computer-independent -- Chaim Frenkel

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Chaim Frenkel
>>>>> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes: NW> Also, how about just $@->id? Shorter and I would argue the "unique_" is NW> really redundant (id's are usually unique, hence the name NW> "identifiers"). Not rea

Re: RFC 94 (v1) Rename @ARGV to @ARGS

2000-08-11 Thread Chaim Frenkel
RL> http://dev.perl.org/rfc/ PRL> =head1 TITLE PRL> Rename @ARGV to @ARGS PRL> =head1 VERSION PRL>Maintainer: Nathan Wiger <[EMAIL PROTECTED]> PRL>Date: 11 Aug 2000 PRL>Version: 1 PRL>Status: Developing PRL>Mailing List: [EMAIL PROTECTED]

Re: RFC 80 (v1): Exception objects and classes for builtins

2000-08-11 Thread Chaim Frenkel
ven't used OO in anger. But for me polymorphism is action-at-distance of the worst stripe. Its the cheap and dirty way of doing OO. Let the object determine the calling convention for the method. I see very little reason to have two methods with different signatures. -- Chaim Frenkel

Re: Data type and attribute syntax (was Re: RFC 89 (v1) Controllable Data Typing)

2000-08-11 Thread Chaim Frenkel
>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> At 10:58 AM 8/11/00 -0400, Chaim Frenkel wrote: >> Someone on this list (TomC?) has supplied a major diatribe against const. DS> Maybe, but I don't see what's wrong with: DS> m

Re: RFC 80 (v1): Exception objects and classes for builtins

2000-08-11 Thread Chaim Frenkel
er else was going PC> on and restore any invariants. Err, how does one differentiate between a 'good' entry and a 'bad' entry. PC> Note too that we don't need to do any case based magic, we can and PC> should use polymorphism for that. Why? Just because? -- Cha

Re: RFC 76 (v1) Builtin: reduce

2000-08-11 Thread Chaim Frenkel
>>>>> "GB" == Graham Barr <[EMAIL PROTECTED]> writes: GB> On Thu, Aug 10, 2000 at 07:22:21PM -0400, Chaim Frenkel wrote: >> Okay, then for >> >> reduce &avg $identity, @list >> >> What should $identity be? GB> I would like

Re: Data type and attribute syntax (was Re: RFC 89 (v1) Controllable Data Typing)

2000-08-11 Thread Chaim Frenkel
ecify types and attributes within a sub JH> prototype? It would be nice to guarantee that subs don't mutate particular JH> parameters, that certain data will not be aliased, etc, so that appropriate JH> optimisations can be done. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-11 Thread Chaim Frenkel
.4567" AS>(_not_ 123.4567) represents error 4567. People will still try AS>stupid floating-point math tricks to get at the suberror code, but AS>at least we'll know they didn't read the bit in the documentation AS>where it will specifically warn _not_ to

Re: RFC 80 (v1): Exception objects and classes for builtins

2000-08-10 Thread Chaim Frenkel
nguages, as you have done above. I just found the PS> try/throw/catch syntax really appealing, and it was a bonus that PS> it would be instantly familiar to the C++/Java crowd. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 85 (v1) All perl generated errors should have a

2000-08-10 Thread Chaim Frenkel
tions welcome. PS> I made a start in RFC 80. Have you looked at the current scheme used by lexical warnings? Hmm, I thought I saw another exception RFC pass by. . Yup, RFC 88, Tony Olekshy <[EMAIL PROTECTED]> Could you two folks get together and hash this out. (I think Graham's

Re: RFC 84 (v1) Replace => (stringifying comma) with =>

2000-08-10 Thread Chaim Frenkel
ld be used on a pair reference: >> >> print key $array[0];# or perhaps: print keys $array[0]; JE> ^^^ Makes sense Mismatch ^ ^ >> print value $array[0]; # or perhaps: print value $array[0]; JE>

Re: RFC 84 (v1) Replace => (stringifying comma) with =>

2000-08-10 Thread Chaim Frenkel
troduce PRL> two new built-ins -- C and C -- to access the components of a pair. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 76 (v1) Builtin: reduce

2000-08-10 Thread Chaim Frenkel
rom (for + and *, you'll usually AS> pick an appropriate identity element). By writing AS> @sum = reduce __+__ 0, @numbers AS> you deal elegantly with both cases. AS> NOTE: I find this trick very elegant. I wish it were my trick, AS> instead of Damian's...

Re: RFC 73 (v1) All Perl core functions should return ob

2000-08-10 Thread Chaim Frenkel
it does now. Hmm, would it be too nasty for perl to recognize that all foo's have the same prototype? (Consider the singular foo case.) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 80 (v1): Exception objects and classes for builtins

2000-08-10 Thread Chaim Frenkel
>>>>> "GB" == Graham Barr <[EMAIL PROTECTED]> writes: GB> On Thu, Aug 10, 2000 at 04:34:50PM -0400, Chaim Frenkel wrote: >> Nice. >> >> The continue clause, I assume would re-raise an uncaught exception. >> But, a big but. How does th

Re: RFC 78 (v1) Improved Module Versioning And Searching

2000-08-10 Thread Chaim Frenkel
plicitly tucks it into a variable BT> whose name starts with main::. E.g. let Net/FTP.pm post its debug BT> flag into $main::Net::FTP::Debug, and the list of exception classes BT> requested of Fatal.pm could be posted into @main::Fatal. -- Chaim Fre

Re: RFC 80 (v1): Exception objects and classes for builtins

2000-08-10 Thread Chaim Frenkel
case __->isa('IO') { ... } GB> case __->isa('Socket') { ... } GB> else { ... } GB> } GB> } GB> continue { GB> # code always executed (ie finally) GB> } GB> And th

Re: RFC 76 (v1) Builtin: reduce

2000-08-10 Thread Chaim Frenkel
ontext (for things to make sense). Why? reduce should be able to reduce a set of matrices to a matrix. Or actually any aggregate (plural whatzit). I think this is too limiting. Depending upon the context reduce should return undef, an empty list, or other empty plural whatzit. -- Chaim

Re: RFC 80 (v1) Exception objects and classes for builti

2000-08-10 Thread Chaim Frenkel
; instead of "otherwise", JP> because sometimes you'll do this: JP> try { JP> # fragile code JP> } JP> catch { JP> # handle other exceptions JP> }; JP> And it would look silly to use "otherwise" there.

Re: RFC 73 (v1) All Perl core functions should return ob

2000-08-10 Thread Chaim Frenkel
DC> sub enervate (?$) : lvalue { $_[0] } DC> And then: DC> non_lazy( a(), enervate(b()), c() ); -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 73 (v1) All Perl core functions should return ob

2000-08-09 Thread Chaim Frenkel
it be available to both? (and of course the opposite eval{}, to make it evaluate the arguments immediately.) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Overloading && ||

2000-08-09 Thread Chaim Frenkel
$token = Perl::Lexer($TDIN)->next_token or $line = <$TDIN>; $line = s/frobitz/knob/g; $token = Perl::Lexer->push($line); We can get real dirty here. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

  1   2   >