On Sun, Sep 6, 2009 at 6:51 AM, Keith Lazuka<[email protected]> wrote: > But before I can do that, I need to get control of where and how the > prettyprinter decides to print each object based on its type. The > biggest hack right now is that in order to make the vocab names in the > USING:/IN: lists a light gray color, I have to rely on the fact that > those strings are passed through and styled by the "presented-text" > word rather than something more obvious like a pprint* method defined > on vocab. I would feel more comfortable if I was hooking into a place > that was strictly intended for vocab names or was actually dispatched > on the vocab type. Another basic question is how should the > "presented-text" word be used?
I think you're looking for the pprint-vocab word in the vocabs.prettyprint vocabulary. > Another strange thing that I have found is that when the prettyprinter > prints a stack effect by itself, then the pprint* word is dispatched > on the effect type. But when the prettyprinter prints a stack effect > as part of a word definition, it does not call effect's pprint* method > implementation. This makes it difficult to highlight the stack effect. This is because the syntax for an effect literal (( -- )) is different from the syntax for a stack effect declaration ( -- ). You probably should look at the stack-effect. word in the see vocabulary for the latter. Slava ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
