diff --git a/Source/NSDebug.m b/Source/NSDebug.m index f8b2a33c0..47943f466 100644 --- a/Source/NSDebug.m +++ b/Source/NSDebug.m @@ -91,15 +91,16 @@ static const char* _GSDebugAllocationListAll(); @end /** - * This function is a GNUstep extension. It activates or - * deactivates object allocation debugging. Returns the - * previous state. You should call this function to activate - * allocation debugging before using any of the functions - * described in this section. Object allocation debugging + * This function activates or deactivates object allocation debugging.
+ * Returns the previous state.
+ * You should call this function to activate + * allocation debugging before using any of the other allocation + * debugging functions such as GSDebugAllocationList() or + * GSDebugAllocationTotal().
+ * Object allocation debugging * should not affect performance too much, and is very useful * as it allows you to monitor how many objects of each class - * your application has allocated. See below for a detailed - * description of the info you can get, and why it is useful. + * your application has allocated. */ BOOL GSDebugAllocationActive(BOOL active) @@ -112,14 +113,14 @@ GSDebugAllocationActive(BOOL active) } /** - * This function is a GNUstep extension. It activates - * tracking all allocated instances of the specified class - * (passed as argument). This tracking can slow your + * This function activates tracking all allocated instances of + * the specified class c.
+ * This tracking can slow your * application down, so you should use it only when you are * into serious debugging. Usually, you will monitor your - * application by using the functions GSDebugAllocationList - * and similia (see above), which do not slow things down - * much and return the number of allocated instances; when + * application by using the functions GSDebugAllocationList() + * and similar, which do not slow things down much and return + * the number of allocated instances; when * (if) by studying the reports generated by these functions * you have found a leak of objects of a certain class, and * if you can't figure out how to fix it by looking at the @@ -280,7 +281,7 @@ GSDebugAllocationAdd(Class c, id o) /** *

- * This function is a GNUstep extension. Returns the number + * Returns the number * of instances of the specified class which are currently * allocated. This number is very important to detect memory * leaks. If you notice that this number is constantly @@ -294,10 +295,10 @@ GSDebugAllocationAdd(Class c, id o) *

* This function, like the ones below, returns the number of * objects allocated/released from the time when - * GSDebugAllocationActive was first called. A negative + * GSDebugAllocationActive() was first called. A negative * number means that in total, there are less objects of this * class allocated now than there were when you called - * GSDebugAllocationActive; a positive one means there are + * GSDebugAllocationActive(); a positive one means there are * more. *

*/ @@ -317,8 +318,8 @@ GSDebugAllocationCount(Class c) } /** - * This function is a GNUstep extension. Returns the total - * number of instances of the specified class which have been + * Returns the total + * number of instances of the specified class c which have been * allocated - basically the number of times you have * allocated an object of this class. If this number is very * high, it means you are creating a lot of objects of this @@ -349,7 +350,7 @@ GSDebugAllocationTotal(Class c) } /** - * This function is a GNUstep extension. Returns the peak + * Returns the peak * number of instances of the specified class which have been * concurrently allocated. If this number is very high, it * means at some point in time you had a situation with a @@ -376,13 +377,13 @@ GSDebugAllocationPeak(Class c) } /** - * This function is a GNUstep extension. Returns a NULL + * This function returns a NULL * terminated array listing all the classes for which * statistical information has been collected. Usually, you * call this function, and then loop on all the classes returned, * and for each one you get current, peak and total count by - * using GSDebugAllocationCount, GSDebugAllocationPeak and - * GSDebugAllocationTotal. + * using GSDebugAllocationCount(), GSDebugAllocationPeak() and + * GSDebugAllocationTotal(). */ Class * GSDebugAllocationClassList() @@ -410,7 +411,7 @@ GSDebugAllocationClassList() } /** - * This function is a GNUstep extension. Returns a newline + * This function returns a newline * separated list of the classes which have instances * allocated, and the instance counts. If the 'changeFlag' * argument is YES then the list gives the number of @@ -508,11 +509,11 @@ _GSDebugAllocationList(BOOL difference) } /** - * This function is a GNUstep extension. Returns a newline + * This function returns a newline * separated list of the classes which have had instances * allocated at any point, and the total count of the number * of instances allocated for each class. The difference with - * GSDebugAllocationList is that this function returns also + * GSDebugAllocationList() is that this function returns also * classes which have no objects allocated at the moment, but * which had in the past. */ @@ -639,10 +640,10 @@ GSDebugAllocationRemove(Class c, id o) } /** - * This function is a GNUstep extension. Returns an array + * This function returns an array * containing all the allocated objects of a certain class - * which have been recorded (to start the recording, you need - * to invoke GSDebugAllocationActiveRecordedObjects). + * which have been recorded ... to start the recording, you need + * to invoke GSDebugAllocationActiveRecordedObjects(). * Presumably, you will immediately call -description on them * to find out the objects you are leaking. The objects are * returned in an array, so until the array is autoreleased, diff --git a/Source/Unicode.m b/Source/Unicode.m index 6ca3baab6..ae7b5fe77 100644 --- a/Source/Unicode.m +++ b/Source/Unicode.m @@ -859,6 +859,7 @@ tables: spos++; break; } + i++; } } dpos++;