So the questions are:
1) Is it possible to do this with gcc without basically rewriting it
from the ground up?
I doubt it. gcc is an old compiler. I haven't looked at the source, so
I'm just making this up, but I'd be surprised if the parser didn't
include at least some state information (ie some level/type of FSM).
I've written recursivedescent parsers. The problem in that case would
be that I couldn't guarantee anything on-the-fly. I suppose I might
have a symbol table available, but essentially this would require
on-the-fly compiling; I'm not sure gcc is able to separate its actions
like this. I'd like to know if anyone thinks or knows if I'm right or
wrong.
2) Would Apple consider supporting/doing this kind of work so that?
it would be so cool, I grant you.
3) How hard would it be to rework XCode to use this?
I believe apple writes some pretty good, extensible code. Because xcode
is already an interface to gcc, I would expect that this sort of
functionality wouldn't be too difficult on the front end, if the back
end (gcc) was available.
I await corrections,
Markian
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
