Re: RFC 157 (v1) Delete C and C commands.

CREAT to a newbie. People have enough trouble with 0644. Now, this doesn't mean dbmopen() has to remain as a builtin. It could be written as a pure Perl wrapper around tie() and AnyDBM_File. But keep it somewhere. Its useful and its not bothering anyone. -- Michael G Schwern ht

Re: RFC 111 (v1) Whitespace and Here Docs

Okay, devil's advocate. Paragraphs. sub legal { print <

Re: RFC 157 (v1) Delete C and C commands.

ry used by core modules. As I said before, this is all nickel and dime stuff. None of it is going to make a real difference. The heart of the matter is should Perl's core functions remain monolithic, or should they be split up into modules? And if they should be split, can we do it just as efficie

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

t doesn't add any functionality and its 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

Re: RFC 114 (v2) Perl resource configuration

cript also makes a good prototype, to hash out the pros and cons of this RFC should anyone want to go forward with it. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Maybe they hooked you

Re: RFC 114 (v2) Perl resource configuration

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>

Re: RFC 114 (v2) Perl resource configuration

ere, put it in /etc/profile. A well configured system will handle it from there. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse BOFH excuse #405: Sysadmins unavailable because they are in a meeting talking about why they are unavailable so much.

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

ate. This has 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

Re: RFC 114 (v2) Perl resource configuration

>handle it from there. > > Not all 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,

Re: RFC 114 (v2) Perl resource configuration

makes more 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

use for this feature. There's been a few half-hearted 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 un

Re: RFC 192 (v1) Undef values ne value

to propose a tighter subcase of this warning 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 An

Re: Quantum computing

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 Co

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

oke.c + docs in perl5) The disambiguation of a 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 "Non

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

On Mon, Sep 04, 2000 at 05:36:32PM -0700, Nathan Wiger wrote: > Actually, the two started merged. :-) They were split up after there > were too many people for RFC 111 but against RFC 162. Personally, I'd > rather see the recipe method of: > >print < > I can't think of much else I'd want to c

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

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 Stu

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

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/

Re: RFC 208 (v1) crypt() default salt

multiple crypt() impelementations (ie. DES vs MD5 vs whatever). -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse Sometimes these hairstyles are exaggerated beyond the laws of physics

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

editors). The # syntax is simple and doesn't involve any of the nesting or accidentally 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/~schwe

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

oblem. I can't think of a 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

Re: RFC 42 - Request For New Pragma: Shell

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.

erwise). 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

Re: RFC 42 - Request For New Pragma: Shell

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 abs

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

;t you just 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/

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

On Wed, Sep 13, 2000 at 11:34:20PM -0700, Glenn Linderman wrote: > The rest is handled adequately and consistently today, and Tom's > dequote is adequate to eliminate leading white space... especially > among people who cannot agree that a tab in a file means "mod 8" > (which it does). Damnit, I'

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

railing whitespace -- 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 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs)

ar = < but these subs [dequote] work in perl 5 today, so don't really need > to be part of the RFC They most definately do. If we're going to propose them as a solution to the indented here-doc problem, it would be best to distribute a collection of commonly used ones as a module

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

ode right or left, it breaks (due to the \s{8}) and you're back to 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: Drop here docs altogether? (was Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs))

noring expansion issues. Thus if an end-tag was lead off by "\t EOF" it would strip exectly "\t " off the front. Any solution: indented tag, regex, dequote... all have the same problems with tabs. They cause more problems than they're worth, you shouldn't be usi

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

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 performanc

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

com, copy and purge $! $ @sys$login:a.com $ copy %s sys$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

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

On Thu, Sep 14, 2000 at 03:36:10PM -0700, Nathan Wiger wrote: > See, this is just too inflexible. The main complaint that I've heard has > been "You can't have leading or trailing whitespace around your > terminator". This is a very common error made by everyone, and *this* is > where Perl should

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

't expand them. Consider them as a literal character. This assums that the code author is going to use the same keystrokes to indent their here-doc text as the terminator, about as safe an assumption as any for tabs. Maybe I'm being too simplistic, I don't use tabs anymore. -- M

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

ly-To. This is BCC'd to perl6-internals). -- 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

int I > wrote that...) If we move it into the core 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. -- M

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

reason I saw was that $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 cr

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

you should enumerate the RFCs you're 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!

iencies of untyped pseudo-hash access. Pseudo-hashes made some 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

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

is already widely-used as 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

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

ng style which involves encapsulation, but I'll concede the point. However, how often do you find yourself with the name of a package in a variable and the function hardcoded? Seems a strange occasion since rarely will two non-OO packages implement interchangable functions. If you find

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

> I like it. But I'm all RFC'ed out, so it's yours, baby... ;-) RFC ho! > [Nate drinks a beer to try and ease the pain of 4 RFC retractions and > another 22 that just need updating.] If you'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 245 (v1) Add new C keyword to DWIM for clearing values

.org/msg00184.html -- 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!

ee this > retained. 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

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

ped down version of Exporter::import(), but keep Exporter around for the special cases. > Actually, any reason not to just plain replace the require keyword with > UNIVERSAL::require altogether? You keep forgetting about: require "some/file/which/is/not/a/module.pl";

Re: RFC 252 (v1) Interpolation of subroutines

proposed that scalars and arrays should interpolate. -- 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: C pragma

m the holy wars which rage between C<$cgi->param('foo')> and C 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 Pe

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

stake will become silent and not be noticed 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/~s

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

direct analogy to print(). "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 C&quo

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

es not understand regexes. They typically have no idea what they're missing. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse make a channel called Perl, and infest it with joking and funit doesnt make alot of sense.

Re: RFC 252 (v1) Interpolation of subroutines

e. Within actual double quotes, it would be hard to pass > parameters that also used double quotes, but within qq// that would > be less of a problem. Fortunately somebody's already proven the feasibility of implementing this sort of balancing. print qq{My foo is $h->{foo}.\

Re: RFC 258 (v1) Distinguish packed binary data from printable strings

hat for your binary vs text string detection you can hijack the existing code for -T and -B file tests. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse ScHWeRnsChweRNsChWE

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

his problem: > > RFC 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

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

luck') ); Carp::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

Re: RFC 21 (v2) Subroutines: Replace C with a generic C function

On Tue, Sep 19, 2000 at 07:47:58AM -, Perl6 RFC Librarian wrote: > Subroutines: Replace C with a generic C function Just as long as I can still say: return want 'LIST' ? @some_array : $some_scalar; I'll be happy. And, of course, want 'L

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

On Tue, Sep 19, 2000 at 01:19:05PM -0400, John Porter wrote: > Michael G Schwern wrote: > > Would anyone find it useful to have a UNIVERSAL method which reports > > on what sybols a given module exports? > > I don't see any reason why this should be anything other th

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

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

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

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

can dig up some p5p threads on the subject. -- 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

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 Ashur

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

"Use of '\$1' detected at line \$.\n". "Perhaps you meant '$term'?\n" if /(peterbuilt|$term)/i && $term ne \$1; s/$term/;/g; } Filter::Util::Call's way of doing things is j

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

e a better interface. If nothing else, 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 103 (v2) Fix C<$pkg::$var> precedence issues with parsing of C<::>

idered modules, which isn't feasible. You could have require() differenciate by whether or not the EXPR matches /::/, but that stinks of a special case. C isn't that hard, but I wouldn't mind seeing a more obvious way. > $mypkg = 'Some::Package::Na

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

als. It may 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 hairst

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

ntations without fragmenting CPAN. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Only mindless violence can raise my spirits now!

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

w/add_entry total_price delete_entry .../ > > 1; > > package Vendor::ShoppingBasket > > use ex::implements ShoppingBasket There's also Class::Virtual (on CPAN) and AbstractClass (on PerlMonks). -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobo

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

impossible to prototype. PS I just ran exactly into your example 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

JWZ on s/Java/Perl/

out overriding existing methods.) This causes no abstraction-breakage, since code which cares couldn't, by definition, be calling the new, ``externally-defined'' methods. o It comes with hash tables, but not qsort? Thanks! o There is no way to access link() on Unix, w

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

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: > &g

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

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 "expe

Re: JWZ on s/Java/Perl/

ways of detecting the OS at run-time 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/

uires core mod or XS). Once that's 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/ ScHWeRnsChweRNsChWErN SchweRN SCHWErNSChwERnsCHwERN sChWErn

Re: JWZ on s/Java/Perl/

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/ I've heard that sem

We're overcaffinated!

ogrammer's shrunken eye)? etc... -- 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!

type. That's what I thought, 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

Why shouldn't sleep(0.5) DWIM?

Why 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?

hat should handle it. The nice part 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 l

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

undef, undef, 0.25) work 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?

architectural > 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?

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/ Hey Schwern! honk, honk, honk, honk, ho

Re: Really auto autoloaded modules

ied functions SYNOPSIS use 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 automagic

Re: Really auto autoloaded modules

ybe I can do something with UNIVERSAL::exports. -- 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

sider Class::Accessor, Class::Class or Class::MethodMaker (those are for methods, which are not important, but the same technique works for funcitons). Or even CGI.pm's brand of autoloading (using strings in a hash instead of the usual subroutines after __END__). -- Michael G. Schwern <[EMAI

Re: Really auto autoloaded modules

yet undetermined) function registry (a glorified hash), loads the appropriate 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...)

this for a while now. Another problem is the fact that not everything on CPAN installs easily. Most does, but some 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. -- Michae

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

, look at the CPANTS synopsis http:[EMAIL PROTECTED]/msg00148.html Its vapor yet, but its all within the realm of "solved problems". -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ BOFH excuse #301: appears to be a Slow/Narrow SCSI-0 Interface problem

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

ong with the bytecode you windup needing a par-style utility anyway. 4) What Brenden said 5) Do YOU have a stable bytecode compiler?? I don't. Perhaps it wasn't clear, I don't mean to have par as part of 6.0, I mean to have it out, like, maybe next month if I dec

Re: Closures and default lexical-scope for subs

3 + 4 is correct and this print 1 + 2 + 3 + 4 is a syntax error. Is it really worth adding that sort of madness to save one character-per-line? Anyhow, I could be completely wrong about how the discussion turned out. Check the archives. -- Michael G. Schwern <[EMAIL

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

le bytecode compiler?? I don't. > > For perl 6? No. Not yet. Is perlcc considered really stable and usable in 5.6? Hmm, my little test would say no. :( > I assumed that since you were discussing this on a perl 6 mailing list, you > were talking about doing this with perl 6. W

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

ts common, and we have a well-developed Perl module for it. Later it can be changed to anything we want. Encapsulation++ -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Maybe they hooked you up with one of those ass-making magazines. -- brian d. foy

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

, wedging the docs into the program) *plus* the normal man page generation and install. That's how I normally do things. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Only mindless violence can raise my spirits now!

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

ird. I remember there being a Very Deep XS Bug that we couldn't quite dig out a while ago. Or maybe it was in Archive::Tar... one of the two. Anyhow, I'm not worried about them much. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Any sufficiently encapsulated hack is no longer a hack.

Re: Larry's Apocalypse 1

t main(...)" in every C program. Then again, we already have to do the #! thing. > Then it might be easier to write modules that are testable without a test > driver. If you run the module directly, some distinguished block of code > could be executed that wouldn't be if the

Re: Larry's Apocalypse 1

one liners? Hmm... programs that have perl one-liners inside them might be troublesome. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One What makes an animal escape from danger? Whe

Re: Larry's Apocalypse 1

largely independent of its compiler once it is compiled and installed, interpreted programs do not have this luxury. Think of it this way... what would happen if Borne Shell suddenly decided it was going to introduce fundemental incompatibilities? (I'm sure they already have...) -- Michae

Re: Larry's Apocalypse 1

;s try to do so not have another three years of having to repeat "What does perl -v say? Ahh, 5.x.x. There's your problem. Try perl6 -v." Not critical, but it would be nice. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assuranc

Re: Larry's Apocalypse 1

d under another name. It was quite common. It is a servicable solution, just be ready for the extra problems. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One ...and that, children

Re: Thinking about scalars

each defines a specific context in which the > operator exists: (string) + (string) or (number) + (number), or some > horrid abberation thereof, which aught not to be. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One AY! The ground beef, she is burning my groin! http://sluggy.com/d/990105.html

Re: Strings vs Numbers (Re: Tying & Overloading)

distinguish between different operators. This will lead to subtle bugs because someone accidentally put a space after the . and didn't notice. Its just cutting it too thin. Don't go this route unless others are exhausted first. -- Michael G. Schwern <[EMAIL PROTECTED]>

Re: Sane "+" string concat proposal

#x27; be numeric as well since one of the sides is unquoted? Probably not what you wanted. This problem will happen with any complex expression which you can't easily put quotes around. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assur

Re: Sane "+" string concat proposal

is the root of the problemPerl 5 version is easy to > understand, Perl 6 version is still ambiguous The Perl 5 version is also ambiguous as you didn't catch the precidence problem I noted eariler. ;) -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobo

  1   2   3   4   >