Re: RFC 196 (v1) More direct syntax for hashes

2000-09-07 Thread Michael G Schwern
edge towards the latter because the former is simple enough to reproduce (just explicitly say Csort keys %hash) and its use is mostly when you want to iterate over the keys of a sorted hash, which would largely be eliminated if your proposal returned a 'sorted' hash. -- Michael G Schwern

Re: RFC 196 (v1) More direct syntax for hashes

2000-09-07 Thread Michael G Schwern
On Thu, Sep 07, 2000 at 10:22:17PM -0600, Nathan Torkington wrote: Michael G Schwern writes: I was expecting those two crufty features to be removed. If they aren't, a third won't hurt. Might want to add this assumption to the RFC. Or perhaps another RFC to junk reset()'s current meaning

Re: RFC 237 (v1) hashes should interpolate in double-quoted strings

2000-09-15 Thread Michael G Schwern
oo 42 bar 13 The idea of interpolating a hash is cool... but is seperating each pair by $/ really useful? A comma or $" sees to make more sense. Could you show some examples of practical usage? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]

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

2000-09-18 Thread Michael G Schwern
and assume that by the time users start writing programs with numbers 2**31 they'll have read that far. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Our business in life

Re: Cross-referencing RFC 186 with RFC 183 and RFC 79

2000-09-14 Thread Michael G Schwern
n to muddle the perl core with test switches, it can be done easier as a module. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse BOFH excuse #39: terrorist activities

Re: Cross-referencing RFC 186 with RFC 183 and RFC 79

2000-09-14 Thread Michael G Schwern
m. You're probably thinking of individual programs. $ pod2tests --inplace foo.pl foo.pl.ok Something like that would make sense. Eliminating redundancy is one thing, eliminating TMTOWTDI is another. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTE

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

2000-09-17 Thread Michael G Schwern
Case-sensitive vs insensitive filesystems, maximum filename length, maximum path length, restrictions on the filename, restrictions on the suffix (ie. 8.3 DOS). Maybe we should just go back to paper. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stu

Re: RFC 190 (v1) Objects : NEXT pseudoclass for method redispatch

2000-09-01 Thread Michael G Schwern
On Fri, Sep 01, 2000 at 08:59:10PM -, Perl6 RFC Librarian wrote: This RFC proposes a new pseudoclass named CNEXT. This pseudoclass would provide a way of correctly redispatching a method or an autoloaded method. Yay! I have nothing constructive to say. (Yay!) -- Michael G Schwern

Re: RFC 189 (v1) Objects : Hierarchical calls to initializers and destructors

2000-09-02 Thread Michael G Schwern
. Also, its not entirely clear why method chaining is desired only for constructor and destructors. What about every other method? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse BOFH excuse

Re: RFC 193 (v1) Objects : Core support for method delegation

2000-09-04 Thread Michael G Schwern
oned Class::Classless. Does any other language or system implement deligations? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Long, long time ago, in a far away galaxy, cells were for

Re: RFC 200 (v1) Objects: Revamp tie to support extensibility (Massive tie changes)

2000-09-07 Thread Michael G Schwern
e as being tied to a given class at compile time, similar to the my Dog $spot syntax ick. Again, I think the issue of translation is a red herring. I believe the problem to lie elsewhere. Ask on p5p and try compiling perl5 with gprof to see where the problem is. -- Michael G Schwern

Re: RFC 200 (v1) Objects: Revamp tie to support extensibility (Massive tie changes)

2000-09-10 Thread Michael G Schwern
more work than the simple method aliasing for the OO/tie hybrid. And in the case of locking a key in a hash, you can't do it because lock() will receive the value. If the code is intended to be run *only* on tied variables, then you could have just used a plain object and dropped the sugar. --

Re: RFC 200 (v1) Objects: Revamp tie to support extensibility (Massive tie changes)

2000-09-10 Thread Michael G Schwern
. The dangling untie() will happen less frequently, and you can customize the hell out of your tied class. But you're trading those problems for a new set of ambiguities! PS Your reply to Fowler hasn't hit the archives yet, so I'll hold off on jumping on his points until then. -- Michael G Sc

Re: RFC 200 (v1) Objects: Revamp tie to support extensibility (Massive tie changes)

2000-09-10 Thread Michael G Schwern
*can* currently be inherited. package Tie; sub TIESCALAR { print "Tie::TIESCALAR\n" } package Foo; @ISA = qw(Tie); package Bar; tie $thingy, "Foo"' Calls Tie::TIESCALAR, as expected. -- Michael G Schwern http://www.pobox.com/~

Re: RFC 200 (v1) Objects: Revamp tie to support extensibility (Massive tie changes)

2000-09-10 Thread Michael G Schwern
different than what was expected. The problem is that Matrix::add() and Some::Module::add() are related by name *only* and are not interchangable. The danger is of methods unintentionally being called in place of unrelated functions. -- Michael G Schwern http://www.pobox.com/~schwern/ [E

RFC - Interpolation of method calls

2000-09-14 Thread Michael G Schwern
=head1 TITLE Interpolation of method calls =head1 VERSION Maintainer: Michael G Schwern [EMAIL PROTECTED] Date: 14 Sep 2000 Version:1 Mailing List: [EMAIL PROTECTED] =head1 ABSTRACT Method calls should interpolate in double-quoted strings, and similar locations

Re: RFC 218 (v1) Cmy Dog $spot is just an assertion

2000-09-14 Thread Michael G Schwern
On Thu, Sep 14, 2000 at 02:19:38PM +0100, Piers Cawley wrote: Michael G Schwern [EMAIL PROTECTED] writes: package Dog; use fields qw(this night up); my Dog $ph = []; $ph-{this} = "that"; That works? I thought you had to do: my Dog $self = fields

Re: RFC 222 (v1) Interpolation of method calls

2000-09-15 Thread Michael G Schwern
ariable method calls. That is: my $meth = 'species'; print "How much is that $pet-$meth() in the window?"; This should deparse to: my $meth = 'species'; print "How much is that ".$pet-$meth()." in the window?"; -- Michael G Schwern http://www.pobox.com/~s

Re: RFC - Interpolation of method calls

2000-09-17 Thread Michael G Schwern
to have a new version of the RFC ready without the first even having made it out to the public! -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Many people think that an UFO is probably

Re: RFC - Interpolation of method calls

2000-09-17 Thread Michael G Schwern
, my font doesn't even display them right. *grumble* -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse BOFH excuse #270: Someone has messed up the kernel pointers

Re: RFC 163 (v2) Objects: Autoaccessors for object data structures

2000-09-18 Thread Michael G Schwern
toaccessor = @{[@stuff]}; If we make it copy the value of @stuff first (like $r-autoaccessor = [@stuff] currently does) then this all encourages inefficiencies. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl

Re: RFC 163 (v2) Objects: Autoaccessors for object data structures

2000-09-18 Thread Michael G Schwern
sure I understand ("autoderef bad, but forced copy bad too") but want to make 100% sure. That's about it. *grunt* -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Plus I reme

Re: RFC 254 (v1) Class Collections: Provide the ability to overload classes

2000-09-18 Thread Michael G Schwern
); bless $inner = $class.'::db'; } It works, but to quote Tim Bunce there... *sigh*. So anyhow, yes, this is a big, icky problem. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse

Re: RFC 218 (v1) Cmy Dog $spot is just an assertion

2000-09-18 Thread Michael G Schwern
On Mon, Sep 18, 2000 at 09:48:27AM +0100, Piers Cawley wrote: Michael G Schwern [EMAIL PROTECTED] writes: Nope. fields::new() basically just does Cbless [\%{"$class\::FIELDS"}], $class, but the current pseudohash implementation doesn't care if something is an object or not

Re: RFC - Interpolation of method calls

2000-09-18 Thread Michael G Schwern
t; already works fine and the world spins on. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse But why? It's such a well designed cesspool of C++ code. Why wouldn't you want to ha

Re: RFC 163 (v2) Objects: Autoaccessors for object data structures

2000-09-18 Thread Michael G Schwern
h has some other restrictions? Read RFC 241 for a brief overview of pseudo-hash problems. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Sometimes these hairstyles are exaggerated beyon

Re: RFC 163 (v2) Objects: Autoaccessors for object data structures

2000-09-18 Thread Michael G Schwern
On Mon, Sep 18, 2000 at 01:26:45PM -0700, Glenn Linderman wrote: Michael G Schwern wrote: Similar mistaken logic leads to "globals are faster than lexicals". Maybe so, but I'd think lexicals would be faster, because more of the lookup is done at compile time rather than runtime

Re: RFC from a newbie: Method References

2000-12-16 Thread Michael G Schwern
); $meth_ref-(); is equivalent to this.. $obj-foo(@some_stuff); You could even make the meth_ref take additional (or overriding) arguments. Its a good idea, I'll put Class::MethRef on CPAN soon. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/

Re: Stupid Newbie Question

2001-11-08 Thread Michael G Schwern
to tcl or python, cuz I can never find clear information about whether such an analog exists in those languages) is going away: AUTOLOAD. Going away? No way, it's SPREADING! We might wind up with AUTOGLOB, too. http://dev.perl.org/rfc/324.pod -- Michael G. Schwern [EMAIL PROTECTED]http

Re: Stupid Newbie Question

2001-11-08 Thread Michael G Schwern
On Thu, Nov 08, 2001 at 04:21:57PM -0800, John Rudd wrote: So, does this mean my other heart's desire of operator overloading might be coming forth? Yeah, that was mentioned in Apoc and Exewhatever 3. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Perl6 Quality

Re: Stupid Newbie Question

2001-11-15 Thread Michael G Schwern
privacy. (yes, I know you can emulate class variables via package globals like $Class::blah, but I'm trying to look at it in a more uniform point of view so that you can fully treat Classes themselves as being objects) Class::Data::Inheritable anyone? :) -- Michael G. Schwern [EMAIL

Fwd: [Re: [FWP] Comic goodness]

2000-09-15 Thread Michael G Schwern
... Send email to [EMAIL PROTECTED] with message _body_ unsubscribe - End forwarded message - -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Plus I remember being

Re: RFC 238 (v1) length(@ary) deserves a warning

2000-09-15 Thread Michael G Schwern
to overhaul prototyping, cool. But I don't see anything to allow Clength $string and Clength @array live together. Its a big RFC, I probably missed it. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6

Re: RFC 56 (v3) Optional 2nd argument to Cpop() and Cshift()

2000-09-01 Thread Michael G Schwern
not a particularly different or interesting way to do it. #1 is good, assuming it causes an error. It also leaves open the possibility of reverting to #3 at some later date. And pop(@array, 0) should do nothing and produce a warning. Garbage In/Error Out. -- Michael G Schwern http

Re: RFC 114 (v2) Perl resource configuration

2000-09-01 Thread Michael G Schwern
On Fri, Sep 01, 2000 at 07:16:13PM -0400, Uri Guttman wrote: "MGS" == Michael G Schwern [EMAIL PROTECTED] writes: MGS Forcing -T on Will break most existing programs. MGS Makes one-liners annoying. who runs

Re: RFC 114 (v2) Perl resource configuration

2000-09-01 Thread Michael G Schwern
the user's to set. PERL_PRELOAD allows the admin to globally set (in the system shell rc file) the rc files that perl will load. Like any other environment variable which the admin wants to be everywhere, put it in /etc/profile. A well configured system will handle it from there. -- Michael

Re: RFC 56 (v3) Optional 2nd argument to Cpop() and Cshift()

2000-09-01 Thread Michael G Schwern
to be done now, unless you use splice(). I've never had it get in my way or had a situation where I needed to swap pop() and shift(). Has anyone else? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee

Re: RFC 114 (v2) Perl resource configuration

2000-09-01 Thread Michael G Schwern
shells -- nor shell invocations -- attend to that file. Yeah, well, that's not my problem that people don't use the One True Shell. ;) Actually, there is a utility out there for universal shell configuration. I've forgotten what its called, though. :( -- Michael G Schwern http

Re: RFC 114 (v2) Perl resource configuration

2000-09-01 Thread Michael G Schwern
sense than -w. Same general problems all 'round. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse MORONS!

Re: RFC 114 (v2) Perl resource configuration

2000-09-02 Thread Michael G Schwern
d attempts at things this might be useful for maybe, but it all boils down to "somebody will find it useful to do something somewhere." I'd suggest we put a hold on further discussion about caveats and implementations until someone really justifies this thing. -- Michael G Schwern

Re: RFC 192 (v1) Undef values ne value

2000-09-04 Thread Michael G Schwern
ing which encompases the conditionals you described. Ignoring warnings should be a conscious decision on the part of the programmer, NOT a fiat by the language designer. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant

Re: Quantum computing

2000-09-04 Thread Michael G Schwern
Steve Fink uddered: Can't quite run perl yet. Not for lack of trying. ftp://cpan.valueclick.com/CPAN/authors/id/D/DC/DCONWAY/Quantum-Superpositions-1.03.tar.gz -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-04 Thread Michael G Schwern
here-doc start from a binary left shift might add serious complexity to th parser. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse "None of our men are "experts."... because

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-04 Thread Michael G Schwern
or your here-doc tag will always work. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse BOFH excuse #356: the daemons! the daemons! the terrible daemons!

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

2000-09-07 Thread Michael G Schwern
On Wed, Sep 06, 2000 at 06:39:38PM -, Perl6 RFC Librarian wrote: =head1 TITLE Retire chop(). Awww, does this mean we won't be seeing chip() and chimp() in Perl 6? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant

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

2000-09-07 Thread Michael G Schwern
On Thu, Sep 07, 2000 at 06:48:35PM -0600, Tom Christiansen wrote: Awww, does this mean we won't be seeing chip() and chimp() in Perl 6? 'Pends on whether you modulate them. KCHP 1570 on your AM dial! -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just

Re: RFC 217 (v1) POD needs comment command. POD needs a reorder command.

2000-09-13 Thread Michael G Schwern
ntally run-on ambiguities of multi-line comments. Its also alot easier to parse. PS Keep in mind that =for can be replaced with =begin/=end in all cases. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee

Re: RFC 216 (v1) POD should tolerate white space.

2000-09-13 Thread Michael G Schwern
time when I've ever put an '=' flush left. I'm sure this has come up on p5p before, but I can't find anything relevent in the archives. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse B

Re: RFC 42 - Request For New Pragma: Shell

2000-09-13 Thread Michael G Schwern
Sooo... what happens to the existing Shell.pm? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse MORONS!

Re: RFC 217 (v1) POD needs comment command. POD needs a reorder command.

2000-09-13 Thread Michael G Schwern
). In fact, I like "=for somewhere else" :) -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Like you've never accidentally spanked a midget. -- Siobain http://www.goats.c

Re: RFC 42 - Request For New Pragma: Shell

2000-09-13 Thread Michael G Schwern
On Wed, Sep 13, 2000 at 07:48:23AM -0400, Bryan C . Warnock wrote: On Wed, 13 Sep 2000, Michael G Schwern wrote: Sooo... what happens to the existing Shell.pm? The RFC title notwithstanding, the pragma would be, by convention, lowercase. (As reflected in the abstract.) The nasty abiguity

Re: RFC 215 (v2) More defaulting to $_

2000-09-13 Thread Michael G Schwern
ust delete the print statement? Unless you're doing some sort of *really* weird stuff with tied filehandles. That aside, could you expand on this and give some examples to show how it will make life easier? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-14 Thread Michael G Schwern
OR } } } } } By combining two of the solutions, my problem is solved. I can indent my here-docs and yet keep the output a single line. Show me where this fails and I'll shut up about it. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTE

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-14 Thread Michael G Schwern
mount of space a tag is indented is the amount which will be clipped off of each line of the here-doc. Tabs will BNOT be expanded. 2. POD end tags may now be followed by trailing whitespace -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Anoth

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-14 Thread Michael G Schwern
it would be best to distribute a collection of commonly used ones as a module with perl. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse slick and shiny crust over my hairy anus constipation sucks -- Ken Flagg

Re: Drop here docs altogether? (was Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs))

2000-09-14 Thread Michael G Schwern
o counting whitespace again. And as Glen pointed out, what about that leading newline? Can I scream now? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse MORONS!

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-14 Thread Michael G Schwern
On Thu, Sep 14, 2000 at 02:51:14PM -0700, Glenn Linderman wrote: Michael G Schwern wrote: Well, OK, so now we're talking shades of opinion. You'd agree it works, though, and quite effectively. But you'd disagree about its aesthetics, and its performance. The former is much less

Re: RFC 226 (v1) Selective interpolation in single quotish context.

2000-09-14 Thread Michael G Schwern
$login:*.* $ purge sys$login:$filename $! $ exit but its not very idiomatic and YMMV. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse I worship Satan and Santa likes me

Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

2000-09-15 Thread Michael G Schwern
ons glibly. TAG } } } } Right? You're not going to just indent the terminator because you can. Its going to go along with indenting the text. So indenting the terminator and indenting the text are linked. If you do one, you want to do the other. -- Michael G Schwern http://www.pobox.co

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

2000-09-15 Thread Michael G Schwern
). -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse When faced with desperate circumstances, we must adapt. - Seven of Nine

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

2000-09-15 Thread Michael G Schwern
the availablity of C compilers is no longer an issue. Having had a taste of the hacks one must do to pull off an all-perl version, XS seems the simplest route. PS I've moved this discussion to perl6-language. Reply accordingly. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL

Re: RFC 71 (v2) Legacy Perl $pkg'var should die

2000-09-15 Thread Michael G Schwern
$hash{a'b} doesn't DWIM... not exactly a stunning problem. (Yes, I am the author of D'oh::Year ;) -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse An ice cream has its unique frequencyAre

Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

2000-09-16 Thread Michael G Schwern
conflicting with. PS Shouldn't this be on perl6-language-objects? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Cheating is often more efficient. - Seven of Nine

Re: RFC 241 (v1) Pseudo-hashes must die!

2000-09-16 Thread Michael G Schwern
sense in the restrictions of Perl 5 syntax, but we've got room now to rethink the problem from scratch. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse But unluckily most Germans here

Re: RFC 71 (v2) Legacy Perl $pkg'var should die

2000-09-16 Thread Michael G Schwern
s a single-quote, so That's a good argument. Unambiguating the language and simplifying the parser. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse When faced with desperate circumstance

Re: RFC 103 (v2) Fix C$pkg::$var precedence issues with parsing of C::

2000-09-16 Thread Michael G Schwern
ngable functions. If you find yourself needing that sort of thing often, perhaps it should be rewritten as OO. I'm feelin' an RFC retraction comin' on... [Schwern rubs his black gloved hands gleefully and cuts another notch into his black hat.] -- Michael G Schwern http

Re: RFC 103 (v2) Fix C$pkg::$var precedence issues with parsing of C::

2000-09-16 Thread Michael G Schwern
u're coming to YAPC::Europe, I definately owe you a few beers. If nothing else than for the hell I've been giving you over here-docs. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse MORONS!

Re: RFC 241 (v1) Pseudo-hashes must die!

2000-09-17 Thread Michael G Schwern
. RFC 122 talks about implementing hashes which are C-like structs in Perl. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Don't ask me, lady. I live in beer. -- fish http

Re: RFC 252 (v1) Interpolation of subroutines

2000-09-18 Thread Michael G Schwern
. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse I'm not cute, I'm evil. -- Diablo www.goats.com

Re: RFC 223 (v1) Objects: Cuse invocant pragma

2000-09-18 Thread Michael G Schwern
') and Cparam('foo') regularly, I can see why it is desired. But it doesn't have to be easy. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse But why? It's such a well designed cesspool of C

Re: RFC 253 (v1) UNIVERSAL::require()

2000-09-18 Thread Michael G Schwern
until much futher on down in the code. Garbage In, Error Out. If you really want it, the wrapper require() is trivial. DTRT? Data Terminal Ready, Tim? Document Filing and Retrieval Tedium? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid

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

2000-09-18 Thread Michael G Schwern
. "printf is like print, except..." which makes it much easier to explain. It provides that bit of mental runway to get the reader's mind off the ground. The differences between sprintf and printf are very easy to explain. "Equivalent to Cprint sprintf" -- Michael G Sch

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

2000-09-18 Thread Michael G Schwern
rime example is fixed-width data parsing. Most people reach for substr() or a regex, but the best solution (as pointed out in perlfaq5) is pack. Yet it still remains obtuse and I'm largely cargo-culting when I use it. Think about a user who does not understand regexes. They typically have no ide

Re: RFC 259 (v1) Builtins : Make use of hashref context for garrulous builtins

2000-09-19 Thread Michael G Schwern
37: Positional Return Lists Considered Harmful RFC 127: Sane resolution to large function returns Don't forget RFC 48 which discusses a localtime() replacement returning a hash. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant

Re: RFC 257 (v1) UNIVERSAL::import()

2000-09-19 Thread Michael G Schwern
cluck('The Royal Air Force does not allow chickens to '. 'fly planes!'); } -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse But why? It's such a well de

Re: RFC 257 (v1) UNIVERSAL::import()

2000-09-19 Thread Michael G Schwern
On Tue, Sep 19, 2000 at 08:06:58AM -0700, Nathan Wiger wrote: If exports() could take arbitrary symbols, just like @EXPORT Yes, that's the idea. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-21 Thread Michael G Schwern
CAPS LOCK KEY STUCK STOP CANNOT PROGRAM PERL REVERTING TO BASIC STOP SEND HELP QUICK STOP -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse When faced with desperate circumstances, we

Re: RFC 266 (v1) Any scalar can be a hash key

2000-09-21 Thread Michael G Schwern
. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Maybe they hooked you up with one of those ass-making magazines. -- brian d foy as misheard by Michael G Schwern

Re: RFC 267 (v1) Eliminate dump() function

2000-09-21 Thread Michael G Schwern
On Thu, Sep 21, 2000 at 03:55:21AM -, Perl6 RFC Librarian wrote: Eliminate dump() function I didn't even know it existed. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Any

Re: RFC 264 (v1) Provide a standard module to simplify the creation of source filters

2000-09-21 Thread Michael G Schwern
"Perhaps you meant '$term'?\n" if /(peterbuilt|$term)/i $term ne \$1; s/$term/;/g; } Filter::Util::Call's way of doing things is just too twisted and strange. Anyhow, I guess this is an elaborate "me too&

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

2000-09-18 Thread Michael G Schwern
we'll get a perlpacktut man page. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse If you only hear one song this year there's something terribly wrong with you.

Re: RFC 236 (v1) Change the way $SIG{__WARN__} and $SIG{__DIE__} are used

2000-09-15 Thread Michael G Schwern
even be that we should kill them and replace them with something better. Has this yet been discussed? -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Sometimes these hairstyles

Re: RFC on Coexistance and simulaneous use of multiple module version s?

2001-01-26 Thread Michael G Schwern
G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Only mindless violence can raise my spirits now!

Re: RFC195: Do not remove 'chop' PLEASE!

2001-01-27 Thread Michael G Schwern
the other day dealing with Text::Wrap guts. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ BOFH excuse #69: knot in cables caused data stream to become twisted and kinked

Re: RFC195: Do not remove 'chop' PLEASE!

2001-01-27 Thread Michael G Schwern
On Sun, Jan 28, 2001 at 01:26:09AM +0100, [EMAIL PROTECTED] wrote: On Sat, Jan 27, 2001 at 05:13:23PM -0500, Michael G Schwern wrote: This one not only modifies its arguments (or $_ when called without), it also has the right prototype and works on lists: sub chop (@) { my

Re: RFC195: Do not remove 'chop' PLEASE!

2001-01-28 Thread Michael G Schwern
On Sun, Jan 28, 2001 at 04:28:08PM +0100, [EMAIL PROTECTED] wrote: Aliasing again. They keys are copies, the values aliases. How bizarre? Why does it work that way? -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ "None of our men are "experts."...

Re: JWZ on s/Java/Perl/

2001-01-28 Thread Michael G Schwern
under Windows, mostly through MFC junk or peeking in the registry. It would probably be good to do it for the MacOS versions, too. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ That which stirs me, stirs everything. -- Squonk Opera, "Spoon"

Re: JWZ on s/Java/Perl/

2001-01-28 Thread Michael G Schwern
done, the rest is just a matter of extending File::Spec (trivial and pure Perl). -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ mendel ScHWeRnsChweRNsChWErN SchweRN SCHWErNSChwERnsCHwERN sChWErn ScHWeRn schweRn sCHWErN

Re: JWZ on s/Java/Perl/

2001-01-28 Thread Michael G Schwern
On Mon, Jan 29, 2001 at 12:10:31AM -0600, Jarkko Hietaniemi wrote: Trivial? *cough* *snigger* I'd write it up for you right now, but its too big to fit in the margin. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Skrewtape I've heard that semen tastes

We're overcaffinated!

2001-01-29 Thread Michael G Schwern
... -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ And it's made from all-natural baby skin, so you know it's good for the environment. http://www.goats.com/archive/000606.html

Re: RFC195: Do not remove 'chop' PLEASE!

2001-01-29 Thread Michael G Schwern
t, but no. The hash effect is pervasive and chop() now has a simple prototype of @ in 5.7.0. (where before it was undefined) -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Plus I remember being impressed with Ada because you could write an infinite loop without

Why shouldn't sleep(0.5) DWIM?

2001-01-30 Thread Michael G Schwern
can't Perl? Smells like a C holdover to me. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ If you have to shoot, shoot! Don't talk. -- Tuco, "The Good, The Bad And The Ugly"

Re: Why shouldn't sleep(0.5) DWIM?

2001-01-31 Thread Michael G Schwern
is it doesn't really require any code translations, you can get away with overriding the core functions instead: sub sleep { CORE::sleep(int($_[0])); } sub alarm { CORE::alarm(int($_[0])); } sub time { int CORE::time } something like that. hand-wave -- Michael G. Schwern

Re: Why shouldn't sleep(0.5) DWIM?

2001-01-31 Thread Michael G Schwern
on those? Or doesn't it? -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Any sufficiently encapsulated hack is no longer a hack.

Re: Why shouldn't sleep(0.5) DWIM?

2001-01-31 Thread Michael G Schwern
standpoint. Perhaps some of the more grossly UNIX specific things like getpwnam's extended family and the SysV IPC stuff? -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ MERV GRIFFIN!

Re: Why shouldn't sleep(0.5) DWIM?

2001-02-01 Thread Michael G Schwern
On Wed, Jan 31, 2001 at 04:44:00PM -0600, Jarkko Hietaniemi wrote: Or explore various garbage collection alternatives. No good, the mob wouldn't be happy. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ purl Hey Schwern! honk, honk, honk, honk, honk, honk, honk

Re: Really auto autoloaded modules

2001-02-01 Thread Michael G Schwern
AnyLoader; Carp::croak("This is going to hurt the Perl community more than it ". "is going to hurt you!"); Its not quite what you're talking about (yet) but we can extend it to flesh out the idea of automagical autoloading. -- Michael G. Schwer

Re: Really auto autoloaded modules

2001-02-01 Thread Michael G Schwern
. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ Summer sun beats down I sigh and wait for winter warm paste enemas. -- mjd

Re: Really auto autoloaded modules

2001-02-02 Thread Michael G Schwern
priate module and exports the appropriate function. PS Actually, it REALLY exists because Arnar came up with a neat trick and I ran with it. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ The eye opening delightful morning taste of expired cheese bits in sour milk!

Re: Auto-install (was autoloaded...)

2001-02-08 Thread Michael G Schwern
require certain interaction and configuration (LWP, Net::FTP, most any DBD driver...). Those can't be done automagically, but if we could do 80% then that's ok. -- Michael G. Schwern [EMAIL PROTECTED]http://www.pobox.com/~schwern/ If you have to shoot, shoot! Don't talk

  1   2   3   4   >