Joe, Eventually I might do something like that; when I implement multi- methods, it might make sense for the parser to always expect ( after the word name. For now, I'm enforcing this in the compiler, not the parser.
By the way, the COM code defines some words with 'define'. Can you update it to use 'define-declared' please? The new stack effect literal syntax (look at (() might help. Slava On Jun 9, 2008, at 1:29 PM, Joe Groff wrote: >> It might make sense to require all definitions to have a stack >> effect, > and have a shorthand parsing word for defining constant words. The > CONST: word could ensure that the definition consists of nothing but > literals and other const words, automatically apply "inline" and any > other optimizer annotations that make sense, and maybe even figure out > the types of the literals and annotate the stack effect with them. For > example: > > CONST: FOO_BAR_BAS "foo" "bar" "bas" ; > > could expand out to: > > : FOO_BAR_BAS ( -- |string |string |string ) > "foo" "bar" "bas" ; inline const ! etc. > > -Joe > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Factor-talk mailing list > Factor-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/factor-talk ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
