Re: Multiple-dispatch on functions

2001-08-31 Thread Me
Dan, I don't immediately see how per object/class dispatch control helps to make multimethods pluggable. Perhaps a multimethod (a set of methods) is a class/object? Is there a general mop for dispatch? More generally: > Yes. Ordinary subroutine overloading (like that offered by C++) > certainly

Re: CLOS multiple dispatch

2001-08-31 Thread Me
> If the dispatcher is drop-in replacable, what does its > interface look like? I'm thinking this is either deep in mop territory, or a probably quite straightforward set of decisions about dispatch tables, depending on how you look at things. I found just one relevant occurence of 'mop' in perl

Re: Source/Program metadata from within a program

2001-08-31 Thread Michael G Schwern
On Fri, Aug 31, 2001 at 11:25:17AM +0100, Nicholas Clark wrote: > Who said that my source file handle was seekable? The problem is, it appears DATA is only opened if there's an __END__ or __DATA__ tag. I don't remember it working this way... *shrug* We can fix that easy. :) -- Michael G. Sc

Re: Source/Program metadata from within a program

2001-08-31 Thread Michael G Schwern
On Fri, Aug 31, 2001 at 10:04:00AM -0400, John Porter wrote: > Brent Dax wrote: > > > use Fcntl qw(:seek); > > > seek DATA, 0, SEEK_SET; > > > @code = ; > > > > IMHO, that's too hackish--just reading that doesn't make what you're > > doing obvious. > > It also can only get the main p

RE: Source/Program metadata from within a program

2001-08-31 Thread Garrett Goebel
From: Nicholas Clark [mailto:[EMAIL PROTECTED]] > On Thu, Aug 30, 2001, Brent Dax wrote: > > From: Michael G Schwern [mailto:[EMAIL PROTECTED]] > > # On Fri, Aug 31, 2001, Bryan C. Warnock wrote: > > # > Access to the source code. > > # > > # Already got that. > > # > > # use Fcntl qw(:seek);

Re: RFC 289 (v1) Generate module dependencies easily

2001-08-31 Thread Steve Simmons
> Perl6 should ship with a simple utility that shows all modules a program > uses, and all modules those modules use. Presumably with the caveat that no usage list can be generated for any missing modules.

Re: Source/Program metadata from within a program

2001-08-31 Thread John Porter
> > > Access to the source code. > > > > Particularly comments and POD. > > Cool--I'd suggest a special $*CODE filehandle, to match $*DATA First, take a look at RFC 79, which I think addresses the wants here. My thoughts on how it should work are a little different now, but I guess it's too la

Re: Source/Program metadata from within a program

2001-08-31 Thread John Porter
Brent Dax wrote: > > use Fcntl qw(:seek); > > seek DATA, 0, SEEK_SET; > > @code = ; > > IMHO, that's too hackish--just reading that doesn't make what you're > doing obvious. It also can only get the main program, not any of the modules it loads. -- John Porter