> fossil and sqlite solve that somehow by being compiled :-) -- they just
> compile the information from those manifest files in their final
> executable, but thats not a reasonable approach for scripts that are
> executed by an interpreter.
Actually, both fossil and sqlite use their build interpreter ('make' and
'tcl' respectively) to process the manifest files into source code. What
stops your interpreter from doing the same? It could perform all the
functions you require, perhaps using additional info made available through
the manifest.
Personally I've always considered 'in source' markers as a bad hack,
rooted in now ancient tools (SCCS/1972 and RCS/1982). I'm not against the
idea per se, but I would like to understand your requirements better. Could
you elaborate?
Thanks,
Paul
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
