<div class="gmail_quote">On Wed, Mar 3, 2010 at 8:15 AM, Eric Noulard <span dir="ltr"><<a href="mailto:eric.noulard@gmail.com">eric.noulard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
2010/3/3 David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>>:<br>
<div class="im">> The CMake generator for Xcode simply uses object pointers as the seed for<br>
> those hex ids: that's why they change every time you run cmake. It's also<br>
> what makes it easy to guarantee that those ids are unique without having a<br>
> data structure to track it.<br>
> Re-using the same ids would be possible, but it would add complexity to the<br>
> xcode generator, and the ids would have to be cached and tracked somehow.<br>
> It's a fairly tall order... If you have the time to propose how to do it,<br>
> perhaps submitting a feature request and a patch to the bug tracker, I would<br>
> be happy to review it.<br>
<br>
</div>Don't know in which case Hex id are used (and I'm not an Mac OS user) but<br>
may be it would be possible to derive those id as a simple hash function<br>
(like <a href="http://sites.google.com/site/murmurhash/" target="_blank">http://sites.google.com/site/murmurhash/</a>)<br>
of something which somehow unique but invariant<br>
like the filename + path + project name + etc...<br>
<br>
Since this kind of function should be fast, may be you do not even<br>
have to cache the hexid.<br>
Theoretically there may be some collision but occurence probability<br>
should be very low.<br>
<br>
My 2 cents idea.<br>
<font color="#888888"></font><br></blockquote><div><br>All good ideas...<br><br>I do not have time or funding to work on these ideas in any sort of near term time frame...<br><br>Patches are welcome.<br><br><br>David<br>
<br></div></div>