Thanks for the reference. Unfortunately it simply suggests that an
aliasref
be used, something that I feel is I'd already looked at and feel
is beyond some of those of our end users who generate the XML
directly,
and are not explicitly programmers.
Also when we generate the XML which the user potentially modifies,
using
less transparent representations will have an intimidating effect, I
think.
You are describing pro-users that will understand the implications of
max lengths. Even more, they usually would NOT want extremely long
paths for readability reasons (I've implemented quite some automation
systems that way).
Most of the discussion is based on implementations dealing INTERNALLY
your data that way and failing mysteriously when PATH_MAX is hit.
For persistence, the typical approach is to PREFER an alias NSData tag
and falling back to an (parallel) path based file reference tag, like
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
