Re: symbol lookup and overload resolution

Stefan Seefeld wrote:
> 
> Does anybody see potential problems with such a separation between
> symbol lookup and overload resolution (and probably more high level
> analysis) ?

Please pardon my ignorance.  Unfortunately, I probably don't currently 
understand the topic well enough to spot any potential problems.  Can 
you point me to a document or a site where I can read up on this?

Also, you said that the symbol lookup would return symbol sets of 
possibly overloaded function names.  What would that look like to an 
ordinary Synopsis user?  Is the symbol lookup something that our own 
visitor classes would call, or is it something that's tucked away inside 
Synopsis itself?  Basically, I'm trying to get a handle on what 
interface my own software (built on top of Synopsis) will see.

> With relatively little efford it will be possible to use the
> redesigned parser for more advanced things that I will try to
> integrate into the synopsis framework step by step, such as code
> generation and various forms of code analysis beyond the 
> documentation extraction that synopsis is currently used for.

That's exciting news.  By the way, I've already been able to build a 
(prototype) code analysis/generation tool on top of Synopsis.  I'm 
looking forward to seeing these new capabilities, too.  I imagine 
they'll make my prototype tool even more useful.

Rick
-- 
Richard M Kelly                             [email protected]
[PGP  =>  D5 C3 CC D2 B7 D0 A9 B0  D5 90 B2 55 5A 80 23 B6  FC AB 67 B4]