>> -3rd=hbide_extrafile=my.txt >> >> I didn't hear back from you what is the problem with >> above solution. >> > > No problem in the above solution until I introduce > this to be embedded into existing implementation in > a transparent way, and believe me, it is really a > big job. I will look into this sometime in future.
Sorry, but I cannot see the complication. You already have a .hbp parser which picks the '-3rd=hbide*' options and sorts them into separate array (you can very easily create another filter which picks the 'extrafile' ones from this list), and it's very easy to generate -3rd options based on that internal array of "extra" files. > I do not question your stance, but BTW, why we cannot > filer it on hbMK2 levels. I simply know that you do not want > but am not aware why. I've already told the reason. The main reason is that Harbour compiler allows to compile any extension, so I don't want to create an extra limit in hbmk2. I find it odd to add extra limitation without very good reason. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
