Hi Marek,
But since dlls are not interchangable (I cannot overwrite one with the
other one) - I am still against renaming them to one common name -
harbour.dll.
Imagine what happens if one installer program installs harbour.dll
in a
system dir and then another one installs Borland harbour.dll in a
system
dir too.
Do you have any kind of solution which would solve this problem in an
elegant way ? ( to convince me to harbour.dll name ? ;-) )
IMO, we should either stick with one compiler when generating
"official" harbour.dll (this may mean a separate, compiler independent
.dll-only binary distribution .zip file), or we can try to make them
interchangeable, if there is any chance to do it.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
