gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The goal of GNUstep 1.0


From: Adrian Robert
Subject: Re: The goal of GNUstep 1.0
Date: Thu, 27 Oct 2005 12:33:02 -0400


On Oct 27, 2005, at 9:06 AM, Fabien VALLON wrote:

On Mer 26 octobre 2005 17:45, Adam Fedor wrote:


What bugs are you talking about? Perhaps we should prioritize the bugs in
the bug database...


Maybye a TODO list ( Roadmap )  before a 1.0 ?
Or maybye put all this TODO list in the bug system with a special
entry/status ?

I checked quickly some classes in AppKit ( with the OpenStep specs ) to
see if all methods are implements :

Great post. This is exactly what we need (IMHO). Then we put them into a task list and prioritize them according to must-have-by-1.0 and otherwise..

In Foundation, NSNumberFormatter still needs work (Fred just recently started on it), and perhaps we should add the NSMessagePort implementation on Windows that Richard has talked about to the 1.0 list? I don't know if someone is willing to work on it, but I feel a fully functional Make/Base (not GUI/Back) on Windows should be prerequisite to 1.0 release.

There are a number of other "FIXME"s in the Base code, but assumedly most of these are icing-on-the-cake that can wait (as, hopefully, are many of the ones in GUI):

---------------------------

./Additions/GCArray.m:  /* FIXME: Check if malloc return 0 */
--
./Additions/GCArray.m:  /* FIXME: Check if malloc return 0 */
--
./Additions/GSCategories.m:  /* FIXME: implement this better */
--
./Additions/Unicode.m:// FIXME check is uni_cop good for this
--
./cifframe.m: /* FIXME: in cifframe_type, return values/arguments that are structures ./cifframe.m- have custom ffi_types with are allocated separately. We should allocate
--
./GSFFCallInvocation.m: See the avcall or vacall man pages for more info. FIXME: I'm betting ./GSFFCallInvocation.m- this won't work if a structure contains another structure */
--
./GSFFCallInvocation.m: * FIXME ... if we have a typed selector, it probably came ./GSFFCallInvocation.m- * from the compiler, and the types of the proxied method
--
./GSFFCallInvocation.m: /* FIXME ... evil hack ... where the compiler did not know ./GSFFCallInvocation.m- * selector types, if may have had to assume a method returning
--
./GSFFIInvocation.m: * FIXME ... if we have a typed selector, it probably came ./GSFFIInvocation.m- * from the compiler, and the types of the proxied method
--
./GSFormat.m: FIXME: I wasn't brave enough to include floating point formatting - ./GSFormat.m- glibc has CPU dependent routines and also uses gmp. So floating point
--
./GSFormat.m: FIXME: This needs to use length, not '\0', when dealing with format
./GSFormat.m-   and %@
--
./GSFormat.m: grouping = ""; // FIXME: grouping info missing in locale?
--
./GSFormat.m: * FIXME - hack to rewrite decimal separator into correct locale
./GSFormat.m-    * if necessary.
--
./GSFormat.m: * FIXME - hack to rewrite decimal separator into correct locale
./GSFormat.m-    * if necessary.
--
./GSLocale.m:  /* FIXME: Get currency format from localeconv */
--
./NSCalendarDate.m: /* FIXME What if the two dates are in different time zones?
./NSCalendarDate.m-    How about daylight savings time?
--
./NSCharacterSet.m:// FIXME ... deprecated ... remove after next release.
--
./NSCharacterSet.m:// FIXME ... deprecated ... remove after next release.
--
./NSConnection.m:         // FIXME thread safety
--
./NSDecimal.m:  // FIXME: this is too small
--
./NSDecimal.m:  // FIXME: this is too big
--
./NSDecimal.m: // FIXME: Here we need a check if the string fits into a GSDecimal,
./NSDecimal.m-  // if not we must round some limbs off.
--
./NSDecimal.m:  // FIXME: Make sure result is big enougth
--
./NSDecimal.m:  // FIXME: I don't understand how to do this
--
./NSDecimalNumber.m:      // FIXME: What exception to raise?
./NSDecimalNumber.m- [NSException raise: @"NSDecimalNumberException"
--
./NSFileManager.m: /* FIXME: On unix, directory accessable == executable, so we simulate that ./NSFileManager.m- here for Windows. Is there a better check for directory access? */
--
./NSFileManager.m: * FIXME ... not sure there is any way to get a creation date :-(
./NSFileManager.m-   * Use the earlier of ctime or mtime
--
./NSInvocation.m: /* FIXME: This only appears on sparc and ppc machines so far. ./NSInvocation.m- structures appear to be aligned on word boundaries.
--
./NSKeyedArchiver.m:// FIXME ... exactly what classes are stored directly???
--
./NSKeyedArchiver.m: _format = NSPropertyListXMLFormat_v1_0; // FIXME ... should be binary.
--
./NSKeyValueObserving.m: * FIXME ... should store an object containing context and options. ./NSKeyValueObserving.m- * For simplicity right now, just store context or a dummy value.
--
./NSKeyValueObserving.m:               * FIXME ... support structures
./NSKeyValueObserving.m- * Unsupported types are quietly ignored ... is that right?
--
./NSNumberFormatter.m: /* FIXME: This is just a quick hack implementation. */
--
./NSNumberFormatter.m:  // FIXME
--
./NSNumberFormatter.m: // FIXME: Should extract separators and attributes
--
./NSNumberFormatter.m: // FIXME: Should extract separators and attributes
--
./NSNumberFormatter.m: /* FIXME: This is just a quick hack implementation. */
--
./NSObject.m:// FIXME - should this be added (as in OS X) now that we have NSKeyedArchiver?
--
./NSObject.m:// FIXME - should this be added (as in OS X) now that we have NSKeyedArchiver?
--
./NSPathUtilities.m: * FIXME ... Check/creation should perhaps be configurable.
./NSPathUtilities.m-   */
--
./NSPathUtilities.m: /* FIXME: Win32 way to get full user name via Net API */
--
./NSPropertyList.m:         // FIXME ... should be immutable sometimes.
--
./NSPropertyList.m:// FIXME ... need to check properly.
--
./NSPropertyList.m:      // FIXME: Get more of the details
--
./NSPropertyList.m:      //FIXME
--
./NSPropertyList.m: // FIXME: We need a better way to determine boolean values!
--
./NSScanner.m:#include <ctype.h> /* FIXME: May go away once I figure out Unicode */
--
./NSScanner.m: * FIXME: I don't use the decimalDigitCharacterSet here since it ./NSScanner.m- * includes many more characters than the ASCII digits. I don't
--
./NSScanner.m: [self notImplemented:_cmd]; /* FIXME */
--
./NSString.m: // FIXME: Need to make mutable array into non-mutable array?
--
./NSString.m: // FIXME ... should normalize composed character sequences.
--
./NSString.m:  /* FIXME ... should remove in future
./NSString.m- * Anything beginning '~@' is assumed to be a windows path specification
--
./NSString.m:  /* FIXME ... should remove in future
./NSString.m- * Anything beginning '~' followed by a single letter is assumed
--
./NSString.m: // FIXME: This does only a normal compare, ignoring locale
--
./NSTimeZone.m:   FIXME?: use leap seconds? */
--
./NSTimeZone.m:          FIXME: Make this more robust. */
--
./NSUndoManager.m: * FIXME: The terms @"Redo" and @"Redo %@" should be localized. ./NSUndoManager.m- * Possibly with the introduction of GSBaseLocalizedString() private
--
./NSUndoManager.m: * FIXME: The terms @"Undo" and @"Undo %@" should be localized. ./NSUndoManager.m- * Possibly with the introduction of GSBaseLocalizedString() private
--
./NSXMLParser.m:        // FIXME
--
./NSXMLParser.m:    type: nil           // FIXME
--
./NSXMLParser.m:    model: nil];        // FIXME
--
./NSXMLParser.m:  return nil;   // FIXME
--
./NSZone.m: memory (glibc malloc does this, what about other mallocs? FIXME).
--
./NSZone.m:#define BUFFER 4 /* Buffer size. FIXME?: Is this a reasonable optimum. */
--
./NSZone.m: FIXME: Optimize code and find a more optimum distribution. */
--
./NSZone.m:  /* FIXME: Do more checking? */
--
./unix/GSRunLoopCtxt.m:         int port_fd_count = 128; // FIXME
--
./win32/Win32_Utilities.m:      // FIXME: Check type is correct!
--
./win32/Win32_Utilities.m: ; // FIXME: Talk to the NET API and get the profile path

---------------------------





reply via email to

[Prev in Thread] Current Thread [Next in Thread]