On Tue, Jun 12, 2007 at 12:25:05PM +0000, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
Currently the code caches all source that is read from .pike files (not .pmod), but I guess that's a bug then.
yup, that was not intended. fixed now. thanks.
Anyway, it's not anywhere near worth the cost to store the source for pure compiled strings for this. Afterall, at least 99.995% of all pike processes won't use any doc extraction at all, and of those that do I'd say at least 80% is perfectly fine with that it only works for normal files.
true. actually, now that the above problem is fixed, a simple switch that can be turned in any script will be enough to start collecting docs. i was under the impression that somehow not all classes created in the beginning came from files. that is of course nonsense. where should they come from?
If you want to cope with code that comes from odd places I think you should provide an API to let other programmers explicitly hook in their class loaders into your doc extraction system. (And such an API should be that the doc extractor can ask the loader for the source when needed, not the other way around.)
can you elaborate on that please?
I don't understand this. All pike sources that are used during the bootstrap comes from normal .pike and .pmod files in the lib directory. It's all there, even the master itself.
right. see above. my mistake.
And btw, I do think it's a very neat feature to get online docs in hilfe. (It's not all gripes. One shouldn't forget the kudos.)
thanks!
greetings, martin.