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

2000-09-18 Thread John Porter
As a solution, a UNIVERSAL:::require() method can be added with the following syntax: $module = "Some::Module"; $module-require; Seems to me that it would need to be written as $module-UNIVERSAL::require; How do you propose to avoid that? What should happen if

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

2000-09-18 Thread Nathan Wiger
John Porter wrote: As a solution, a UNIVERSAL:::require() method can be added with the following syntax: $module = "Some::Module"; $module-require; Seems to me that it would need to be written as $module-UNIVERSAL::require; How do you propose to avoid that?

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

2000-09-18 Thread John Porter
Nathan Wiger wrote: Huh? All classes inherit from UNIVERSAL implicitly. Yes, but at that point in the execution, $module is not a class. It's the same reason you can write: $module-can('dance'); Once upon a time this was not possible. I guess it has changed. -- John Porter

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

2000-09-18 Thread Michael G Schwern
On Mon, Sep 18, 2000 at 11:20:15AM -0400, John Porter wrote: Seems to me that it would need to be written as $module-UNIVERSAL::require; How do you propose to avoid that? What is a class but a package? And what is the name of a class but a package name? And since there's no

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

2000-09-18 Thread John Porter
Michael G Schwern wrote: It all works. Mokay... DTRT? Data Terminal Ready, Tim? Document Filing and Retrieval Tedium? Do The Right Thing, of course. -- John Porter