Massimo Belgrano wrote:
about hbmk2 can you post a little sample (also with minigui) so i
will try
Facts are that Viktor have modified each error post here regarding
hbmk2
I've explained in a post on Sunday:
http://www.hmgforum.com/viewtopic.php?p=5494#p5494
Thank you. [ Sorry, but I'm not following HMG forums. ]
So I understand the problem now.
Current hbmk2 implementation of #include dependency
detection is pretty basic (see NOTE in source), it
only detects '#include "filename"' format and nothing
else. Since I'm not using anything else for me it was
more than enough, and it probably covers 95% of cases,
and even the rest is easy to adapt.
More complex cases can be added, but I don't really
like them as they slow down detection too much for
too little gain.
For your case this wouldn't be enough though.
To cover it, hbmk2 would need real source parsing,
including PP processing to find all such "hidden" header
dependencies. To avoid duplicating PP logic in hbmk2
.prg code, ideally this should better be solved using
some __PP_*() function which returns some information
(in this case array of dependent header filenames).
Depending on how quick this process would be, this
method could either replace one existing level
if dependency detection, or we can add a new one,
like (-head:pp). So, the user interface side is easy
to solve.
I can't solve the PP parser part, but if such
function gets added to core, I'm ready to add support
for it in hbmk2.
Przemek, do you think that such function would be possible
to implement?
__PP_INCLUDELIST( <cPRGFileName>, <cOptions> ) -> <aINCLUDEFileName>
(or something with similar effect)
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
