2015-09-15 11:40 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
Pharo uses them. 

Posix permissions are useful for both linux and mac. 
Windows uses also the posix permissions that came with MinGW… I do not think they are useful but we provide them anyway :)

I removed the mingw based permissions (mingws stat/lstat) because they are slow and don't work with longpath names (neither
with real multibyte paths).



ps: I do not know what are you doing there guys, but you broke my builds (I’m taking a look at them now) :P

improbable, I didn't push the latest code change :)

On 15 Sep 2015, at 09:24, Nicolai Hess <nicolaihess@web.de> wrote:

2015-09-15 4:11 GMT+02:00 Ben Coman <btc@openinworld.com>:

On Sat, Sep 12, 2015 at 11:00 PM, Nicolai Hess <nicolaihess@web.de> wrote:
> 2015-09-10 21:31 GMT+02:00 Eliot Miranda <eliot.miranda@gmail.com>:
>> Hi Nicolai,
>>     I'm a bit concerned that this is creating drift with the "official" Cog source base at http://www.squeakvm.org/svn/squeak/branches/Cog.  Long filename support for win32 was recently added by Marcel Taumel in May of this year.  Are you tracking that?  How can we keep the sources harmonized?
> Ok, I removed all of my code again and merged with sqWin32Directory.c and sqWin32FilePrims.c from the official cog source.
> I left only pharos additions for the fileattributes (posixpermissions) this should make it easier to merge which the
> squeak vm main branch (wrapped with pharo vm ifdefs).

What is the purpose of fileattributes? In the interests of further
minimising drift, is this useful to Squeak?
cheers -ben

I don't know, I don't think we use it at all. And for the different platforms, the permission attributes
doesn't really *are the same*. For example, the read/write permissions we are showing for
win32 platform, don't have much to do with win32 access restrictions - Idon't know about macos.