Hi,

>> Another idea, and this looks the best so far. Why not introduce 
>> a symbol which can be REQUESTed from app code, if someone wants 
>> to enable pcode loading feature?
>> F.e.
>>   REQUEST HB_LIB (or HB_LIBDYN...)
>> This would pull above code from a separate .c file, which .c file 
>> wouldn't be part of harbour*.dll, only reside in static lib with 
>> no reference to it from Harbour code code.
> 
> Yes, this is a solution.
> I though about it but in practice it means that it's necessary to create
> separate library which is not included by harbour*.dll or hack make files
> to exclude single file from harbour shared library. Personally I do not
> like such hacks because sooner or later they are exploited by sth, i.e.
> it's not possible to recompile current Harbour code with HB_DYNLIB macro

Which should never be necessary in normal situation.
IOW if such is required to access any standard Harbour 
feature, it's a bug by itself to be fixed.

> so I would prefer such library though global filter used to excluded files
> from harbour shared library seems to be acceptable.

I'd certainly be better. We can add such extra library 
f.e. by the name 'maindll'.

> I'll commit the modifications in a while so you can decide about final
> form to include exported version of hb_vmProcAddress() function.

Great.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to