> I'm using auto_cache right now, and saw fuse_purge_np is available > from the docs. Are you saying fuse_purge_np may not be there in the > future?
Yes, it may not be. IIRC I did say in those docs that this function is experimental. > libfuse in the same program. Could you enlighten me why one mustn't > linking against both libfuse & MacFUSE.framework? I can see that > having to distribute separate versions of the app as one reason why > it's not desirable to do so, but I'm curious if there are any > technical limitations based on how MacFUSE.framework works. Well you can if really want to. Then you get into the business of having to know and worry about internal details (which MacFUSE.framework links against which libfuse). It's only likely, and not guaranteed, that MacFUSE.framework on Leopard+ will link against ino64. Are you sure your need is not met by auto_cache alone? Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
