Hi Nicholas,

"Nicholas Seckar" <[email protected]> writes:

> Forgive me if some of this already exists and I just haven't found it yet, 
> but...
>   - Applying factor's corrective advice to the source (e.g. Add USING:
>   entries, etc?)

Yup, the USINGs on the TODO. What other corrective advice is available?

>   - Some kind of support for jump-to-error?

It's already in there: type 'g' in the debug buffer that pops up when
compiling a file (C-ck). There's also support for restarts and compiler
info. Is that what you want?

>   - Showing the stack effect of the region under the cursor? (Maybe
>   more experienced Factorsauria don't goof up the stack effects, but I
>   still do.)
>

This would be really cool, but i'd need to learn more about support from
factor to infer the stack effect of a region (it could be done in the
elisp side, i guess, but i doubt it'd be robust enough). Any pointers?

(Slava, you are probably aware of it, so sorry for nagging, but in
merging my branch you missed the patch that fixes the hang of the
listener; it's in the middle of some messy conflict resolution on my
part... sorry for that)

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to