RE: Really auto autoloaded modules

2001-02-04 Thread Dave Storrs
On Sun, 4 Feb 2001 [EMAIL PROTECTED] wrote: > > "Dave" == Dave Storrs <[EMAIL PROTECTED]> writes: > > > Dave> When you want to install a new version, you simply prepend it > Dave> with its version number (or insert it at appropriate place). > > Dave> The order is, of course, irrelevant...y

RE: Really auto autoloaded modules

2001-02-04 Thread Hildo . Biersma
> "Dave" == Dave Storrs <[EMAIL PROTECTED]> writes: Dave> When you want to install a new version, you simply prepend it Dave> with its version number (or insert it at appropriate place). Dave> The order is, of course, irrelevant...you can order it as 1.3, Dave> 2.0, 1.0 if you want, but the

Re: assign to magic name-of-function variable instead of "return"

2001-02-04 Thread James Mastros
On Sun, Feb 04, 2001 at 05:30:59PM +0100, Johan Vromans wrote: > James Mastros <[EMAIL PROTECTED]> writes: > > And I always hated that about VB and Pascal -- you can assign to the magic > > variable, but can't modify it. > > That was before the invention of auto-assignment operators. In the > 70s

Re: Specifying vtable API in terms of macros?

2001-02-04 Thread Edwin Steiner
Dan Sugalski wrote: > > At 05:02 PM 2/3/2001 +0100, Edwin Steiner wrote: > >Might this be madness? (BRAINSTORMS AHEAD!): > > Generally, yes. :) > > The vtable stuff won't be exposed outside the core. This means embedding > programs and extensions will *not* be using it. Generally speaking, it'l

Re: assign to magic name-of-function variable instead of "return"

2001-02-04 Thread Johan Vromans
James Mastros <[EMAIL PROTECTED]> writes: > On Thu, Feb 01, 2001 at 07:36:59PM -0600, David L. Nicol wrote: > And I always hated that about VB and Pascal -- you can assign to the magic > variable, but can't modify it. That was before the invention of auto-assignment operators. In the 70s, Burrou