On Jan 23, 2008, at 2:12 AM, Ken Shmidheiser wrote:

> With the recent discussions concerning FSSpec vs FSRefs,

Just two quick points for all FBers using files with FBtoC:

1) Please read the FBtoC help docs. The OPEN verb, for example, is  
different from FB's OPEN. This is documented.

2) FBtoC supports only an FSSpec or FSRef with the OPEN verb. Again,  
please see the FBtoC docs.

FSSpecs were implemented in FBtoC  so existing code wouldn't break  
(assuming someone was using the most modern FB offered ---FSSpecs) .  
It would have been much easier in FBtoC to use only FSRefs

If you are not using FSSpecs, consider going directly to FSRefs  
instead. FSSpecs do NOT handle long ( > 31 chars) files names and  
your users will call/email asking why their file names have garbage  
in them. Some users won't notice the file name but mangled file names  
can cause other issues including (under the right conditions)  
inadvertent data loss. Apple deprecated FSSpecs for good reasons and  
it wasn't just some whimsical choice to annoy programmers.

Brian S.