Re: callback or call now?

in reply to callback or call now?

I think that you've got it turned around. The common case, in my mind, would be import by ref instead of import by callback. The second slash means "Something a little funny is going on" which would be the callback case, to my mind.

Cheers,
Erik

Light a man a fire, he's warm for a day. Catch a man on fire, and he's warm for the rest of his life. - Terry Pratchet

Comment on Re: callback or call now?

Replies are listed 'Best First'.
Re: Re: callback or call now? by John M. Dlugosz (Monsignor) on Oct 17, 2002 at 18:20 UTC
If backslash simply means "not the default", then its meaning varies with your expectations. I'm thinking that it more-specifically means "take it literally, not as instructions to find the answer.". Then you get this progression: `foo => &bar` means call bar now when the structure is being built. `foo => \&bar` means call bar later, when foo is imported (and bar can see the context of what the impoter is asking for). Finally, `foo => \\&bar` will call bar even later, when foo is actually called after being imported. —John	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: callback or call now?
by John M. Dlugosz (Monsignor) on Oct 17, 2002 at 18:20 UTC

I'm thinking that it more-specifically means "take it literally, not as instructions to find the answer.". Then you get this progression:

foo => &bar means call bar now when the structure is being built. foo => \&bar means call bar later, when foo is imported (and bar can see the context of what the impoter is asking for). Finally, foo => \\&bar will call bar even later, when foo is actually called after being imported.

—John

[reply]
[d/l]
[select]

In Section Meditations