>I think no matter what is decided, consistency-wise, someone is going to be >unhappy with it. If we use DumpCore() the C programmers won't like us, >dump_core() and the C++ and Java programmers will throw fits. I think the >best thing we can do is decide on what -Perl- programmers want. >Unfortunately, this is rather difficult to pin down, but we should probably >take hints from the language itself. Sometimes you must lead, not follow. --tom
- Define consistent and standard Garrett Goebel
- Re: Define consistent and standard Michael Fowler
- Re: Define consistent and standard Leon Brocard
- Re: Define consistent and standard Tom Christiansen
- Re: Define consistent and standard Graham Barr
- Re: Define consistent and standard Michael Fowler
- Re: Define consistent and standard Tom Christiansen
- Re: Define consistent and standard Gisle Aas
- Re: Define consistent and standard Michael Fowler
- Re: Define consistent and standard skud
- Re: Define consistent and standard Bart Lateur
- Re: Define consistent and standard Graham Barr
- RE: Define consistent and standard Garrett Goebel
- RE: Define consistent and standard Garrett Goebel