libs-base/Documentation/ReleaseNotes.gsdoc

194 lines
6.8 KiB
Text
Raw Normal View History

<?xml version="1.0"?>
<!DOCTYPE gsdoc PUBLIC "-//GNUstep//DTD gsdoc 1.0.1//EN" "http://www.gnustep.org/gsdoc-1_0_1.xml">
<gsdoc base="ReleaseNotes">
<head>
<title>GNUstep Base Release Notes</title>
<author name="Adam Fedor">
<email address="fedor@gnu.org"/>
<url url="http://www.gnustep.org/developers/whoiswho.html"/>
</author>
<version>$Revision$</version>
<date>$Date$</date>
</head>
<body>
<chapter>
<heading>Base Release Notes</heading>
<p>
The release notes include descriptions of API changes, behavior
changes and other information that might help developers and users
migrate to using a newer version of the library.
</p>
<section>
<heading>Version 1.10.2</heading>
<p>
</p>
<deflist>
<term>NSContainsRect behavior change</term>
<desc>
The definition of NSContainsRect has changed to
correspond with the current Mac OS X/Cocoa definition. The
sides of the bRect can touch aRect.
</desc>
<term>Unichar file paths</term>
<desc>
Windows supports unichar file paths, but there isn't
really an API for handling this. GNUstep-specific
methods for dealing with this have been
added, <code>NSFileManager's
-localFromOpenStepPath</code> and
<code>openStepPathFromLocal</code> and equivalent methods for
<code>NSString</code>. In most cases the Base library should
handle this problem internally, but it's possible that there
are cases where the developer wants to handle the file name
explicitly with system-specific functions.
</desc>
<term>NSDictionaryErnumerator</term>
<desc>
Some ivars in NSDictionaryEnumerator have changed types,
but the total storage space has not changed. This may
cause problems if you access ivars directly, perhaps
through a subclass.
</desc>
<term>NSNotification -setImmutablePost</term>
<desc>
This GNUstep extension method was removed.
</desc>
<term>NSPort extension methods</term>
<desc>
Unimplemented GNUstep extension methods <code>-close</code>,
<code>-outPackedClass</code>,
and <code>+outPackedClass</code> were removed.
</desc>
<term>NSTimeZone -abbreviationDictionary</term>
<desc>
<code>NSTimeZone</code>'s abbreviation dictionary is now
a proper one-to-one dictionary.
</desc>
</deflist>
</section>
<section>
<heading>Version 1.10.1</heading>
<p>
</p>
<deflist>
<term>Runtime version disconvery of library</term>
<desc>
A developer can discover the version of the base library that
is loaded using the NSBundle methods
<code>[[NSBundle bundleForLibrary: @"gnustep-base"] infoDictionary]</code>
and retrieving the <var>GSBundleVersion</var> key.
</desc>
<term>NSXMLParser class added</term>
<desc>
This is a Cocoa class that has been added for
compatibility. The class is still alpha state.
</desc>
<term>NSArray makeObjectsPerformSelector:</term>
<desc>
The order of iteration through objects was changed to
match Cocoa.
</desc>
<term>Designated initializer changes</term>
<desc>
The designated initializer for NSArray, NSDictionary,
NSSet, and NSString for MacOS X compatibility. Like
MacOS X, you can call <code>[super init]</code> to initialize
the class from a subclass, although it is prefered that you use
the <em>designated initializer</em>, with it's richer
set of initializers.
</desc>
</deflist>
</section>
<section>
<heading>Version 1.10.0</heading>
<p>
</p>
<deflist>
<term>Interface version change</term>
<desc>
The interface version of the base library has changed in
this release, as it will in all future releases with a
new minor number (that's the second number in the
release number). Applications, libraries and tools that
wish to use this new version must be recompiled
(otherwise, they'll use the older version of the library).
There is no single reason for this change. Arguably, it
should have been done long ago.
</desc>
<term>NSString clarification</term>
<desc>
The NSString documentation contains some clarification
on the lifetime of returned NSString objects.
</desc>
<term>URL classes support persistant connections</term>
<desc>
The NSURLHandle and other classes have support for
persistant connections.
</desc>
<term>NSMethodSignature clarification</term>
<desc>
Recent compiler releases have exposed a flaw in the way
GNUstep gathers signature information. The
documentation explains how the information for offset
and registers may not be reliable.
</desc>
<term>Mac OS X compatibility</term>
<desc>
There have been many fixes in various classes for Mac
OS X compatibility, particularly relating to XML encoding.
</desc>
</deflist>
</section>
<section>
<heading>Version 1.9.2</heading>
<p>
</p>
<deflist>
<term>GSMime parsing ignores extraneous data</term>
<desc>
When extraneous data is encountered in the input, it is ignored
(and a warning logged) rather than adding it to the
message body. Not sure this is right though, perhaps we should
raise an exception or extend the api to return the extra
data. Anyway, it's better than the previous behavior of
adding the bad data to the parsed body.
</desc>
<term>New log functions GSOnceFlag and GSOnceMLog</term>
<desc>
Log messages the first time the code is executed. Typical
usage is to log warnings about deprecated features.
</desc>
<term>NSError</term>
<desc>
New MacOSX compatibility class
</desc>
<term>GSObjCRuntime</term>
<desc>
Multiple new runtime functions that work with both GNU
and Apple runtimes. These functions allow you to look
at method lists, add and remove methods (for instance,
if you want to make sure your method in a category
overrides another method in a category).
</desc>
<term>NSProtocolChecker rewritten</term>
<desc>
Was previously almost non-functional.
</desc>
<term>autogsdoc</term>
<desc>
Support added for building frames structured documentation.
Add the flag <code>-MakeFrames YES</code> to the autogsdoc
command line.
</desc>
<term>Binary incompatibilities</term>
<desc>
NSUnarchiver, GSIMapTable have new ivars added to
them. Tools and applications that use these classes may
need to be recompiled after the new library is installed.
</desc>
</deflist>
</section>
</chapter>
</body>
</gsdoc>