> Now this program: > > IN: c > USING: a b ; > > : bar ... \ foo ... ; > > is not the same as this program: > > IN: c > USING: b a ; > > : bar ... \ foo ... ; > > Even though both foo's are quoted using \.
The problem is that the using order matters. Auto-use doesn't know which order to put things in and it shouldn't have to -- name collisions should be a parse error. It would have saved me several _hours_ if this had been a parse error all along. Also, this is fragile because someone can cause a collision in your program by changing another vocabulary -- exactly what we're trying to avoid by talking about escaping all inert symbols. At least this item is on the todo list. ;-) Doug ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
