Hi Alex,
> Perhaps to better emulate the current shell script it could check argv[0] > for the name that defines its expected behaviour. When it is ready to > replace the script then the symlinks will still work on Unix/Linux. On > Windows we will have to put up with a few extra executables which are > identical. I think disk space is the last problem on people's minds these > days. On Windows I think users should use the command line switches. At least that's the most common way on this platform, and there is no compatibility concern here. Of course we may add wrapper batches, to offer a similar environment to *nixes. Best would be if the GNU-make would generate these (instead of storing them on SVN), to be even more on par with *nixes. I'll implement the argv[0] trick, many thanks for the suggestion. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
