Re: DISFAVORED Was: name for 3 PICK finally?

Josh Grams <josh@[EMAIL PROTECTED]
> wrote:
> Jonah Thomas <jethom...@[EMAIL PROTECTED]
> wrote:
> >
> >So, say we make the Forth-94 compile-only words be EXECUTE-ONLY.
> >Get rid of POSTPONE (meaning encourage people not to use it). Let
> >users make words be EXECUTE-ONLY too. An EXECUTE-ONLY word always
> >executes and never gets compiled -- just exactly like IMMEDIATE !
> >But not state-smart. (Meaning encourage people not to use STATE
> >as we've encouraged them for 20+ years.) If you want to wait
> >until later to execute an execute-only word, then put it into a
> >macro and execute the macro whenever you want to.
> 
> How would I put an execute-only word in a macro without using
> POSTPONE (or EVALUATE)?
 
What I'm imagining is that the macro would use EVALUATE . So you never
get an xt for the execute-only word. You can't use COMPILE, on it, or
POSTPONE . 

The result is a simpler system because all the things you can't do don't
need methods to do them. And it's easier to understand because a
collection of methods that are kind of complex to follow are gone.

But the missing functionality might actually get in the way. I'm trying
to see if there are some Gotchas there and not just Yes Buts.