17 Aug
2009
17 Aug
'09
10:45 p.m.
2009/8/17 M M <mostafa_working_away@yahoo.com>:
1) Given this conflict, will you still proceed with the same function name? (As an fyi, all other boost libraries I've incorporated into the iphone fortunately don't have this problem.)
The name was chosen as that's what it's called in S4.1.7 of the UUID RFC: http://www.ietf.org/rfc/rfc4122.txt Do you have a suggestion for a new one?
2) If so, do you have any suggestions on how I can handle this issue besides manually changing the function name from nil to something else?
I think the only other option would be something nasty like this: #define nil empty #include <boost/uuid.hpp> #undef nil