|
From: | Stefan Bidi |
Subject: | Re: Obtaining a UUID NSString |
Date: | Thu, 26 May 2011 16:40:05 -0500 |
I am not in 'dire' need of it, I can substitute it for something else if it is available, tho I would like to reduce the amount of Frameworks I need to link against. Adding the UUID functions to corebase is the best solution to be source compatible, which is what I am aiming for.As of right now, there were only about four or five functions/method/classes in my Cocoa app that were missing from GNUstep's frameworks, and the CoreFoundation UUID functions were one of them (the others I reported).I use CFUUIDRef, CFUUIDCreate, CFUUIDCreateString, and CFRelease.If just those were implemented, and the worked, I would be greatly appreciative. And GNUstep would be one step close to source compatibility with Cocoa.- Thanks,AustinOn May 26, 2011, at 8:19 AM, Stefan Bidi wrote:On Thu, May 26, 2011 at 12:43 AM, Austin Clow <dr_clow@mac.com> wrote:Thank you for your response,
However, -globallyUniqueString contains information (host name, the process ID, a timestamp and a counter), I would prefer a UUID that has no information encoded within it.
- Austin
Is this something you're in dire need of? If so, I can take a look at implementing CFUUID in corebase (as Niels mentioned, it's a CF implementation). I've had little time to work on it lately, but I can make a push and probably get something working around mid to end of June.
Keep in mind, however, that very little is working in corebase right now.
Stef
[Prev in Thread] | Current Thread | [Next in Thread] |