[bug #24784] Thread safety issue with NSCalendarDate...

[Gregory John Casamento]

Follow-up Comment #3, bug #24784 (project gnustep):

For some reason when it reaches the following code in NSLog.m:

      else
        {
          prefix = [NSString
            stringWithFormat: @"%@ %@[%d] ",
---->>      [[NSCalendarDate calendarDate]
              descriptionWithCalendarFormat: @"%Y-%m-%d %H:%M:%S.%F"],
            [[NSProcessInfo processInfo] processName],
            pid];
        }
    }

The line indicated calls the method to instatiate a calendarDate object, but
for some reason in that method it appears that an NSDate is being used.  I'm
not sure why. 

Here's the method that's being called:

+ (id) calendarDate
{
  id    d = [[self alloc] init];

  return AUTORELEASE(d);
}

For some reason, self here is NSDate and NOT NSCalendarDate as one would
expect (given that it was invoked with NSCalendarDate as the class).

Is it possible that this is a thread safety issue in the runtime?

GC


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?24784>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/