>>> Am I right in my observation ? >> >> Partially. It's a freeform format. I hope above >> comments helped to clear it. If not, pls ask. >> > > "FreeForm" format. > And here the trouble begins. > It is possible that you reach to .hbp from .hbi > but is not possible to transfer .hbp to .hbi. > Probably even we do not need it. I simply can > give ext .hbp to .hbi and can contain .hbi > specific sections as you described. It is easy. > It stands valid for new projects. For already > .hbp's these have to be re-created through > hbIDE. If this is acceptable, I can move > in this direction. Such created .hbp will be > valid for hbMK2 and hbIDE both.
I didn't think of this limitation. Let me think about it for a little while, maybe it's possible to create a simple parser, which can be used in HBIDE to read pure .hbp files. If we do it this way, it's enough to use the #HBIDE.section1.var=value trick to include HBIDE specific options/tokens. BTW, hbmk2 also has a -skip option which can be used to abort .hbp file processing. Something what may be useful. I used it already to embed .hbp file inside a .prg. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
