On Tue, 14 Jul 2009, Szak�ts Viktor wrote:
> For MS-DOS and NT/Win9x platforms, the wildcard feature
> isn't needed, as ~1 ending is guaranteed in practice. IMO
> it's even dangerous to have it as it can pick other files
> by accident. I don't know about DOSEMU, DosBox.

I'm now in my office and my short tests with Windows XP shows
that it isn't.
It was enough to use editor which creates backups adding ~ to
original file names and I have:
   CHANGE~1 => ChangeLog~
   CHANGE~2 => ChangeLog
Probably the same effect you can reach by simple:
   ren ChangeLog ChangeLog~
   copy ChangeLog~ ChangeLog
I'll hardcode CHANGE~1 inside hbpp bit for me it's really ugly
hack. I do not find CHANGE~1 worse or better then CHANGE~?
If someone will have few files with such name then it's probably
result of some back system and I do not find anything what allows
me to prefer CHANGE~1 shortcut.

> I also have a patch pending to look for a list of filenames,
> probably it'd be better if you did it.
> I also added 'CHANGES' to the list, maybe we will switch
> in the future. I didn't to it yet, because almost all
> projects use ChangeLog as the de facto std for such file.

Yes, ChangeLog is currently standard name but it really creates
problems for DOS builds. Especially for OpenWatcom which does
not support long file names.
I've just check and it's not easy to move hb_fsFind*() from
RTL to COMMON because it depends on some other C RTL functions
like hb_charUpper() in wild match functions hb_vm[Un]Lock(),
hb_fsSetIOError(), hb_osDecode(). We will have to add dummy
implementation of above functions to hbpp and harbour binaries.
We already have many other of such dummy functions which are used
to create binaries without RTL and HVM so maybe we should create
HBNOVM or HBNORTL library with all of them which can be used to
link harbour, hbpp and other non .prg tools like examples/pp.
It should help in moving some things from RTL to COMMON library.
Now we have to introduce the same modification in few places.

best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to