What about FSCatalogGetInfo? I use that to test the validity of an FSRef and in one odd case, to convert an FSSpec to an FSRef.
Stephen Sent from my iPhone > On Sep 27, 2017, at 1:14 PM, Thomas Tempelmann <[email protected]> wrote: > > Ah, right you are. But that gets you different IDs than you might get from > other APIs. But yes, probably not an issue for most apps. > > And some functions do not work any more at all, such as FSCatalogSearch > (which was quite a problem for my own product, which I solved eventually by > using searchfs now). > >> On Wed, Sep 27, 2017 at 10:12 PM, Martin Crane <[email protected]> wrote: >> As far as I’m aware that case has been taken care of by the Apple engineers, >> and Carbon APIs will not be broken, although there will be an extra overhead >> incurred for their use. >> >> -Martin >> >>> On 27 Sep 2017, at 21:09, Thomas Tempelmann <[email protected]> wrote: >>> >>> Also, everyone keep in mind that on APFS, dirIDs / fileIDs (CNID) are now >>> 64 bit, and the upper bits are actually used (curtesy of the HFS-to-APFS >>> conversion process), so if you use those IDs, they won't be right when read >>> via the Carbon File Mgr APIs. You'll have to use NSURL or the low level BSD >>> functions such as getattrlist, which are a pain to use (but then, if you're >>> still on Carbon, you must be used to that ;) >>> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Carbon-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/carbon-dev/sgreenfield1%40mac.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com This email sent to [email protected]
