david, thanks for your prompt response. you presented an implementation issue as a reason for this behavior - i can understand. however, do you appreciate the issue of user data getting over written each time? in my opinion this represents a serious limitation of cmake on the mac when trying to use it for a large, collaborative project where continuous and frequent updates are required.
you ask me for an alternative: the mac file system is pretty good at keeping track of files independent of file names/paths. couldn't unique file handles/hash ids be obtained from just there? these can be used instead and presumably provide some stability compared to dynamic pointers in memory (the latter change all the time). regards On Wednesday, March 03, 2010, at 12:44PM, "David Cole" <david.c...@kitware.com> wrote: >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
