Path2_copy() function is broken in version 2.0 (fixed in 2.1).
This function is not used within the kit itself.
Unfortunately there are currently a number of problems in GNU Objective-C related to object archiving. Since archiving is central to W3Kit, it is important to be aware of the pitfalls until these bugs are fixed. The first group of bugs will affect many application programmers:
float m; objc_write_array(stream, "c", sizeof(m), &m);While that's not portable, the object archive created by W3Kit will usually be consumed by the same server that produced it.
"[4i]"are not yet supported by most archiving functions.
The second group of bugs will not affect as many application programmers, because the W3Input class (which acts as the base class for most of W3Kit) contains workarounds that protect its subclasses from these bugs:
+setVersion:, in classes which do not derive from W3Input:
extern void class_set_version_fix(Class *class, unsigned num);
+initializemethod are slightly different from those under NeXTSTEP. More importantly, though, the semantics are buggy with respect to archiving:
+initializeappears to only get called before the first class method is called, and unarchiving currently does not automatically invoke any class methods.
WriteGIF()function (copied verbatim from XV source, as required by its license) appears to get confused on images bigger than about 400 X 400. For now, keep your graphics widgets down to this size.
Author: Paul Burchard
Comments to: firstname.lastname@example.org
Created: Apr 18 1994 --- Last modified: Tue Jun 18 10:30:27 1996