Nested projects.
I mean if .hbm includes another .hbm
it should treat it as a nested another project
contrary to current implementation where another .hbm
becomes a part of the current.
May be .hbm implementation be kept as is and a new
extension is introduced, say .hbprj and if encountered,
replace .hbprj with .hbm and treated as nested project
redefining all attributes from .hbprj.
This way I can stay only in one folder and any changes
in related libs ae automatically taken care of. Just like xMate.
Yes, probably some new extension is needed for that,
plus a new processing loop inside hbmk2. Plus possibly
concerting the whole internal hbmk2 process to a self
contained (quasi) object to allow for recursion.
In most cases it would be equivalent to calling hbmk2
multiple times, so I don't really see the time investment
justified yet.
The other important (but optional) part is dependency
detection, but that's too far yet to think about.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
