Jean-Marc Pelletier

Having recently compiled a number of externals on an Intel Mac, I ran accross some unexpected behaviour that forced me to re-examine my code. Specifically:

A function that relied on path_nameconform(fn,fn_conform,PATH_STYLE_NATIVE,PATH_TYPE_ABSOLUTE) had to be changed to PATH_STYLE_SLASH, PATH_TYPE_BOOT to work on Mactel. It seems that PATH_STYLE_NATIVE returns OS9-style colon-sperated paths. Did I miss something, or is this a bug?

file-path-funkiness-on-intel-mac

Not a bug. We're still using HFS style paths and file APIs 

internally, so that is in fact still native. OS X supports both HFS 

Let us know if you have any problems you're not able to work around 

On Oct 3, 2006, at 6:01 PM, Jean-Marc Pelletier wrote:

> Having recently compiled a number of externals on an Intel Mac, I 

> ran accross some unexpected behaviour that forced me to re-examine 

> A function that relied on path_nameconform 

> (fn,fn_conform,PATH_STYLE_NATIVE,PATH_TYPE_ABSOLUTE) had to be 

> changed to PATH_STYLE_SLASH, PATH_TYPE_BOOT to work on Mactel. It 

> seems that PATH_STYLE_NATIVE returns OS9-style colon-sperated 

> paths. Did I miss something, or is this a bug?

Not a bug. We're still using HFS style paths and file APIs  
internally, so that is in fact still native. OS X supports both HFS  
and Uniz style paths.

Let us know if you have any problems you're not able to work around  
with the strategies you've outlined.

>
> Dear all,
>
> Having recently compiled a number of externals on an Intel Mac, I  
> ran accross some unexpected behaviour that forced me to re-examine  
> my code. Specifically:
>
> A function that relied on path_nameconform 
> (fn,fn_conform,PATH_STYLE_NATIVE,PATH_TYPE_ABSOLUTE) had to be  
> changed to PATH_STYLE_SLASH, PATH_TYPE_BOOT to work on Mactel. It  
> seems that PATH_STYLE_NATIVE returns OS9-style colon-sperated  
> paths. Did I miss something, or is this a bug?


Thanks for the reply. I had problems opening files with fopen() and assumed that the path style was at cause. I haven't tried to verify further but I suppose it was rather PATH_TYPE_BOOT/PATH_TYPE_ABSOLUTE that was the cause.

On Oct 4, 2006, at 9:11 PM, Jean-Marc Pelletier wrote:

> Thanks for the reply. I had problems opening files with fopen() and 

> assumed that the path style was at cause.

You are correct, actually. fopen as called through Apple's libraries 

does not support HFS syntax, though other OS X APIs do. fopen under 

>
> Thanks for the reply. I had problems opening files with fopen() and  
> assumed that the path style was at cause.

You are correct, actually. fopen as called through Apple's libraries  
does not support HFS syntax, though other OS X APIs do. fopen under  
CW supported HFS syntax.

File path funkiness on Intel Mac?