Hi Esteban, Guille and Everyone,

I haven't looked at using FFI much, however it is easy to imagine that
different file encoding rules on different platforms will make writing
FFI calls more difficult, i.e. some of the different formats are:

- OSX uses Mac specific decomposed UTF8 encoding
- Windows uses Wide Strings (16 bit Unicode characters)
- Linux allows pretty much anything, but precomposed UTF8 is common

Believe it or not, I'm still working on getting the
FileAttributesPlugin working (file name encoding on Windows being the
latest issue - the tests in Pharo need to be extended).

Would it be useful for future FFI work to have primitives available
which convert file names to and from the various platform specific
formats?  (Linux is basically a no-op, and Windows could be written
in-image, but OSX requires the platform routines to be called).

Cheers,
Alistair

Reply via email to