Re: perl5 to perl6

2001-05-12 Thread Chaim Frenkel
>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes: NT> Chaim Frenkel writes: >> Those are all major typo inducing changes. >> >> You'll need alternative micro-code loads for your fingers, when >> switching between clien

Re: perl5 to perl6

2001-05-11 Thread Chaim Frenkel
^From\s+\S+\s+\S+\s+(\S+\s+\S+)/) { NT> @r = reverse split ' ', $who; NT> @r[0] = sprintf("%02d", @r[0]); NT> %count{"@r"}++; NT> } NT> } NT> foreach (sort %count) { NT> printf("%s: %3

Re: Now, to try again...

2000-12-18 Thread Chaim Frenkel
So having line and offset information available in the output could be made available. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Proposal for groups

2000-12-05 Thread Chaim Frenkel
but no BMK> subscriber could post. Just be careful about the perl6-all redirection. Don't allow registration on both redirection lists. Hmm, How would this work? Headers would be re-written? How would 'critical' comments get to the -internals-design list? -- Chaim Frenkel

Re: Opcodes (was Re: The external interface for the parser piece)

2000-12-02 Thread Chaim Frenkel
m of things we have specific routines DS> for. (I'm no OO programmer) I can't wrap my mind around how one can extend a OO hierarchy so that a low level (i.e. closer to the base class) can know about a future type. (I once tried to work through the Smalltalk hierarchy

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Chaim Frenkel
necessary? Why not a non-vtbl function that knows how to add numeric types? I would have wanted to limit the vtbl to self manipulation functions. Set, get, convert, etc. Cross object operations would/should be outside the realm of the object. (It seems like trying to lift yourself by the bootstraps.) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: The external interface for the parser piece

2000-11-30 Thread Chaim Frenkel
JH> /* any others? */ JH> }; JH> should be used around SVs to ascertain that everything fits everywhere. I was under the impression that p6 was going to do away with p5's incestuous knowledge of hardware bits. And go with a more OO style of dispatch. -- Chaim Frenkel

Re: The external interface for the parser piece

2000-11-29 Thread Chaim Frenkel
cation' that needs to be aware of platform dependencies. Bootstraping could be accomplished with a thin stub layer over FILE *, with progressive iterations of PerlIO replacing the stub. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Backtracking through the source

2000-11-29 Thread Chaim Frenkel
$foo = s;foo;bar;g; $foo = s#foo#bar#g; # change the world -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: The external interface for the parser piece

2000-11-28 Thread Chaim Frenkel
S> Dan Sugalski even samurai DS> [EMAIL PROTECTED] have teddy bears and even DS> teddy bears get drunk -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: To get things started...

2000-11-27 Thread Chaim Frenkel
go. ST> Perhaps we really need a new kind of regex that works by-design against ST> streams of bytes? ST> -sam -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: SvPV*

2000-11-22 Thread Chaim Frenkel
;m more inclined to think of the structured data type as a layer above the raw bits. I see the association of attributes with the underlying data as an extra 'service'. If for no other reason, there are many ways of having the attributes distribute across, deletions, additions, and

Re: To get things started...

2000-11-22 Thread Chaim Frenkel
g. (And that this will be able to parse code at acceptable speed.) Anyway, what does this have to do with the API? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: SvPV*

2000-11-22 Thread Chaim Frenkel
tion. Getting an efficient representation of a meaningful structure should be done a new data type. (I'm thinking of representing COBOL records/data, or even XML documents) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: The new api groups

2000-11-15 Thread Chaim Frenkel
always safe to resubscribe. You'll get an error message if you're on DS> already. I just stick with -all, and let the filter take care of the rest. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: The new api groups

2000-11-14 Thread Chaim Frenkel
e language, etc. Planning a map from "here" to DG> "there" doesn't sound quite feasible when we don't know where "there" is. DG> What am I missing? DG> pete -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-10-31 Thread Chaim Frenkel
threaded code is so much slower; this can also be seen as >> an indictment of threaded code). JvV> Now I am really confused. This directly contradicts the Threaded Perl RFC. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-10-27 Thread Chaim Frenkel
has to be done or not. If there are some magic combinations of operations that are done very regularly, a new word that does that combo could be provided. If the representation doesn't allow for certain optimizations, the TIL is not the optree, but rather the final executable form. The compiler co

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

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-25 Thread Chaim Frenkel
don't see any practical restrictions at all.) We may not even need to copy the body. If the header of the function is target location, the header could any one of nop, nest another inner loop lookup current symbol fixup caller or jump to

Re: [not quite an RFC] shared bytecode/optree

2000-10-25 Thread Chaim Frenkel
As the pieces were pulled off the disk, the next io instruction ended up in the right place. Myth?) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: [not quite an RFC] shared bytecode/optree

2000-10-25 Thread Chaim Frenkel
ps could use relative addressing as not needing relocation. But I'm not sure that all architectures support long enough relative jumps/calls. Doing the actual relocation should be quite fast. I believe that all current executables have to be relocated upon loading.

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-25 Thread Chaim Frenkel
>>>>> "AT" == Adam Turoff <[EMAIL PROTECTED]> writes: AT> On Tue, Oct 24, 2000 at 10:55:29AM -0400, Chaim Frenkel wrote: >> I don't see it. >> >> I would find it extremely akward to allow >> >> thread 1:*foo = \&o

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-24 Thread Chaim Frenkel
.e. using pointers (or direct machine calls) to other body of code made up of pointers or a real piece of code. You seem to be thinking of threaded execution. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-24 Thread Chaim Frenkel
ually done, all threading is directly to the body of &foo. When the *foo assignment is done, copy the &foo body to a new location. replace the old &foo body with an indirection (I believe this is atomic.) And optionally, the indirection could be to a fixup

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-23 Thread Chaim Frenkel
rhaps if there were some dataflow analysis some region of code) to use indirection? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 334 (v1) Perl should allow specially attributed subs to be called as C functions

2000-10-10 Thread Chaim Frenkel
>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: DS> At 01:50 PM 10/10/00 -0400, Chaim Frenkel wrote: >> There is an intermediate method, have our own execution and data stack. >> Basically build a TIL interpreter. This might be intermediat

Re: RFC 334 (v1) Perl should allow specially attributed subs to be called as C functions

2000-10-10 Thread Chaim Frenkel
ion, like: DS>perl_call(perl_cv_ptr, 1, 2, 3); DS> the bad bit about that is it means that calls to perl functions are DS> different than calls to C functions, and I'm trying not to do that--I DS> really do want to be able to get real f

Re: RFC 361 (v1) Simplifying split()

2000-10-05 Thread Chaim Frenkel
this is the sentence ); $bar[0] eq ""; $bar[1] eq "this"; Currently $bar[0] eq "this"; If you think about it isn't removing leading fields, it's looking for the first non-whitespace token on the li

Re: RFC 326 (v1) Symbols, symbols everywhere

2000-10-05 Thread Chaim Frenkel
y, this might be something useful at the user level. Many times I do this @record{@keys} = new_values(); Using a set of 'intern'ed strings might make it more efficient. And unless we are able to note that @keys is always the same,the hashes would have to keep getting recomputed. W

Re: RFC 301 (v1) Cache byte-compiled programs and modules

2000-09-27 Thread Chaim Frenkel
o the cached version. eg. /usr/local/perl/.../Posix.pm.1050:22 # George did this one And this would be disabled under -T -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-09-24 Thread Chaim Frenkel
it be different for different applications running at the same time? How does an application query what the current timezone or zone offset is? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: A common event loop

2000-09-23 Thread Chaim Frenkel
nd expensive way of doing something 'simple'. And I can't imagine how this would work. Any statement could be interupted with an exception, but there is no mechanism to restart. This is just plain wrong. -- Chaim Frenkel

Re: RFC 153 (v2) New pragma 'autoload' to load functions and modules on-demand

2000-09-23 Thread Chaim Frenkel
the tarball) modules that are not judged as requiring a use will be in there. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 23 (v5) Higher order functions

2000-09-23 Thread Chaim Frenkel
1] is DC> parameter [1] is the 2nd parameter. They'll know because at the very start DC> of L I will write: DC> ^1 means $_[1], NOT $_[0] [snip. Last message repeated too many times.] If you have to do that, that is a good argument to follow the '

Re: RFC 260 (v1) More modules

2000-09-22 Thread Chaim Frenkel
process. Please, make the Config.pm be internal. So it can not be seperated from the executable. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 260 (v1) More modules

2000-09-21 Thread Chaim Frenkel
and the rest. The embeded pod documentation is not needed on a production only server. And if the .pm can be boiled down to bytecode then there is no need for the .pm Will you require that the .pm be installed on a production box just so that embedded pod will be available? -- Chaim Frenkel

Re: RFC 260 (v1) More modules

2000-09-21 Thread Chaim Frenkel
7;ve done it wrong. It stays wrong until the machine is replaced. *sigh*, -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 23 (v5) Higher order functions

2000-09-21 Thread Chaim Frenkel
an array. All I ask is the Damian add our comments to the RFC. -- 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-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 260 (v1) More modules

2000-09-20 Thread Chaim Frenkel
nment I have a clean nice place to work from either making a tarball or just using SysV packaging. Why make life hard, an option can be a lot easier than having to manually rm stuff. (I.e. rm everything except perldiag.pod.) And what about when the installation changes? Or .... Perl is a

Re: \z vs \Z vs $

2000-09-20 Thread Chaim Frenkel
rong". Sorry, I'm missing it. $_ = "etc\n"; /etc$/; # true $_ = "etc"; /etc$/; # true In what way is this _wrong_? Is it under /m? But then wouldn't longest match cover the situation? And doesn't it o

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 260 (v1) More modules

2000-09-20 Thread Chaim Frenkel
ation on, have _NO_ direct human users. They are purely application servers. I don't want a minimum stripped down perl installation that will get my job done. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 23 (v5) Higher order functions

2000-09-19 Thread Chaim Frenkel
a newbie, not one of the oldtimers whose been part of perl6 since Damian's RFC came out. Would they think that the second and third arguments were added or the first and second? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 260 (v1) More modules

2000-09-19 Thread Chaim Frenkel
of production machines. I don't need documentation on the production boxes. Or what about a application that doesn't want to force the end-user to install perl? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 100 (v2) Embed full URI support into Perl

2000-09-18 Thread Chaim Frenkel
t; so that the default is to call the uri stuff. Is it just me, but I keep wondering how Uri Guttman gets into this. -- 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 246 (v1) pack/unpack uncontrovercial enhancements

2000-09-18 Thread Chaim Frenkel
e spirit of how pack/unpack is used. PRL> The semantic is enhanced as much as possible under this constaint. PRL> Additional changes to pack/unpack are listed in other proposals. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-09-18 Thread Chaim Frenkel
erence between the syscall idea of time and some 'universal' perl epoch. Then all the programs would need to be able to translate from any OS to any other OS would be the offsets between any system and the perl epoch. Perl would not have to maintain this table it would not have to go out in

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 237 (v1) hashes should interpolate in double-quoted strings

2000-09-17 Thread Chaim Frenkel
initive reason why hashes do not interpolate. And that's PRL> fine by me. What about formating the output as a value that can be used by eval? %hash = (a => 1, b => 'the world'); print "%{hash}\n"; ('a' => 1, 'b'

Re: RFC 214 (v1) Emit warnings and errors based on unoptimized code

2000-09-17 Thread Chaim Frenkel
we can always point at where the line starts, if it still >> exists. TC> Make it: TC> Division by zero error on statement beginning at line xx TC> Consider multiline constants -- where do you say the warning occurred? TC> print < blah TC> bl

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 214 (v1) Emit warnings and errors based on unoptimized code

2000-09-15 Thread Chaim Frenkel
pot they occur, even down to reporting the DS> appropriate failure line in a multiline statement. We don't worry about DS> bloat or slowdown, because the assumption is that -H is only used during DS> debugging or when speed doesn't matter,

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

2000-09-15 Thread Chaim Frenkel
gt; system-dependent, then we have nothing against which to offset it. Just a function/variable that would contain the offset from machine/os system epoch to unix (or universal) epoch. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Chaim Frenkel
should have been honored. Or ... Hmm, that might not be a bad idea at all. There was some talk about reworking the command line. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Chaim Frenkel
, then just rerun the job and add a -T right at the front. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-09-15 Thread Chaim Frenkel
adjustment, CN> were you? Maybe you could state exactly what you propose, because I don't CN> know what it is. Disregard this. I was indicating that _IF_ p6 would honor a TZ variable the lack of a TZ variable could leave the results unchanged for old scripts. Just a way of maintaining

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Chaim Frenkel
yada. No command line switches there. Only the #!. If the subclued webmaster has perl in his cgi-bin directory, -T is his least worry. Hmm, or are you thinking of a shell script that's calling perl? Then he has lots of holes to worry about. -- Chaim Frenkel

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Chaim Frenkel
guments, perl has to process them to know how to interpret the script. The only other mechanism that might be worthwhile would be for perl to notice the -T and then give up and re-exec itself with an added -T at the front of the line. This would be workable as long as none of the -M&#x

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Chaim Frenkel
breach can be caused by not having a -T? The perl code is available to be read. So what can a perl program do that the black hat couldn't by tweaking the code? The code is running under the black hat's priviledges and uid. -- Chaim Frenkel

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-14 Thread Chaim Frenkel
voked PRL> on the commandline, and runs a script that contains the PRL> -T option on the #! line, Perl should just turn on PRL> taint mode and not complain about it. PRL> =head1 MIGRATION ISSUES PRL> None. -- Chaim Frenkel

Re: RFC 214 (v1) Emit warnings and errors based on unoptimized code

2000-09-14 Thread Chaim Frenkel
ut keeping one of the original line numbers would at least point at the correct expression. The only movements that I can see are merges and reorgs. And we can generate a reasonable association to get the users eyeball to where it belongs. -- Chaim Frenkel

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

2000-09-14 Thread Chaim Frenkel
what is the difference between the timestamp returned from the syscalls, and the unix (or whatever) epoch. If you want to adjust for timezones just calculate the constant. Which since you are giving it in HHMM format you might as well just calculate directly. So what am I missi

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

2000-09-14 Thread Chaim Frenkel
hat doesn't use perl's epoch and we need to write a value to a file? I think I've just gotten very confused. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 218 (v1) C is just an assertion

2000-09-13 Thread Chaim Frenkel
# Nothing but declarations. Package Pet; sub Feed(); sub Play(); sub Wash(); sub Pet(); Though how to tell perl to enforce it. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

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

2000-09-13 Thread Chaim Frenkel
ght be useful is have strftime() (or something similar) built-in without having to use POSIX; and the default should be MMDDHHMMSS.fff, (the ISO format) I personally prefer to pass around the string representation, more that perl and unix systems need to handle datetime. (And I find it ea

Re: RFC 214 (v1) Emit warnings and errors based on unoptimized code

2000-09-13 Thread Chaim Frenkel
nce between line numbers/files and op code File cross-reference (might be just the %INC) file#, filename from, to, file#, line# ... If the optimizer moves some opcodes around, it would slice and dice the relevent offset records to keep tr

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 - Prototype RFC Implementations - Seperating the men from the boys.

2000-09-11 Thread Chaim Frenkel
phase. Up until that point, it is wasted energy. At this point, without code there is nothing locked down, no cost in changing. (Yes, even though they are bits, changing software, changing architecture has major costs.) Lets work on firming up the specs and ironing out differences. -- Chaim Frenkel

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: RFC 90 (v3) Arrays: Builtins: merge() and demerge()

2000-09-10 Thread Chaim Frenkel
>>>>> "DC" == Damian Conway <[EMAIL PROTECTED]> writes: DC> I *still* think it should be "unmerge"! ;-) Hrmpf. It should be reshape. (Which would be its own inverse and saves a keyword.) -- Chaim Frenkel

Re: RFC - Prototype RFC Implementations - Seperating the men from the boys.

2000-09-10 Thread Chaim Frenkel
users to be accounted for. And the fact that you are allowing some RFCs to go without a prototype puts this into the _we need an RFC Czar_ tyranny mold. Let the ideas flow for a while, and then let's go back over them for fine-tuning or rejection. -- 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: one question about vtbls

2000-09-10 Thread Chaim Frenkel
d work (waving hands violently) like this, vtbl Integer vtblFloat vtblString vtblDualNaturedVariable etc. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFCs for thread models

2000-09-10 Thread Chaim Frenkel
thread with bar # create new thread with bar while () { push(@a, $workOrder); } } Or for that matter, perhaps @a is file scoped? :shared and my/our are orthogonal. One is cross-thread the other is scoping. -- Ch

Re: Project documents

2000-09-10 Thread Chaim Frenkel
in reserve. Think of Larry as Daddy and all the kids running over when he comes home, He did, No he did, No he, ...) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

  1   2   3   >