Przemyslaw,

Przemysław Czerpak wrote:
> On Mon, 08 Mar 2010, Maurilio Longo wrote:
> 
> I believe that you are right but test on shared volumes is not an answer
> because it may depend on host system behavior which can be different then
> native OS2 one so it would be nice if you can verify it for native local
> volumes too. Just to be sure :)
> 
Tested on a local JFS volume, files with 'A' and 'R' or without flags are
shown by current Directory() call.

> I can try to help in this process but final tests have to be done by real
> OS2 users.
> Seems that the following files should be updated:
>    filesys.c (hb_fsOpen(), hb_fsCreate(), hb_fsCreateEx(), hb_fsClose(),
>               hb_fsSetDevMode()?, hb_fsIsDevice()?
>               hb_fsGetFileTime(), hb_fsEof(),
>               hb_fsRead(), hb_fsWrite(), hb_fsReadLarge(), hb_fsWriteLarge(),
>               hb_fsReadAt() (64bit offsets support),
>               hb_fsWriteAt() (64bit offsets support),
>               hb_fsTruncAt() (64bit offsets support),
>               hb_fsLockLarge() (64bit offsets support),
>               hb_fsSeekLarge() (64bit offsets support),
>               hb_fsDelete(), hb_fsRename(), hb_fsMkDir(), hb_fsChDir(),
>               hb_fsRmDir()
>    fstemp.c
>    fssize.c (it should be updated also for native MS-Win builds to eliminate
>              CRTL stat() function)
>    hbffind.c (hb_fsFindNextLow() (64bit file size support))
> 
> Do you seen any potential problems in switching to native OS2 API in above
> functions?
> 
I don't think that there could be problems, given that in the end CRTL uses
the same APIs. The only problem could come from calling some CRTL with handles
received by native APIs which could not be known to the CRTL.

I remember a problem when I moved a part of xHarbour calls to API native ones,
but I don't remember all the details; that said, if all file I/O goes through
native APIs there can be no problem at all.

Best regards.

Maurilio.

-- 
 __________
|  |  | |__| Maurilio Longo
|_|_|_|____| farmaconsult s.r.l.


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

Reply via email to