Re: Late vs. early binding Was: DISFAVORED Was: name for 3 PICK

On Mar 8, 8:14 am, Josh Grams <j...@[EMAIL PROTECTED]
> wrote:
> The main gotcha that I know of is that someone could redefine one
> of the words you're using in your macros.  I've had that happen to
> me, and it's ugly.  One of the things I like most about Forth is
> the early binding, and I do reuse short common words as internal
> names.  And it just feels wrong to me to have the macro system be
> late binding when the rest of the system is explicitly early
> binding.

Also, if you are using wordlists for namespace management, late-
binding macros are constrained to the namespace order that they are
defined under, while early-binding macros can be ex****ted to a
different wordlist without having to have its definition wordlist
available at macro-runtime.