This is the README for MiscSerialPort2.m [Download] [Browse] [Up]
(o) the user should be warned if trying to set XON/XOFF when in raw mode. (o) in - transmitChars: (const char *)buffer length: (int)length, the status should reflect if the number of characters passed could not be transmitted (o) should the variables defined at the top of the .m file be private ivars? why? (o) should the priority of the fd monitor be "setable" from outside? (o) the status is now an int masked with the constants in the .h in order to reflect several conditions at a time (o) I think that the status is now refreshed each time a state changes in the object. (o) should the lock file name be made available? (o) should NO PARITY be called ZERO PARITY? (o) Warn the user of the risk of infinite PING-PONG if echoing is done when connected to a device that does it as well. (o) the use of bitfields in the flags structure made some sense when I had 12 flags but now that I've "decentralized" them the two-byte gain is probably not worth the hassle of the "flags.???" each t ime they're accessed. (o) NEXTSTEP support: stringValue, setStringValue, target/action, palette object. (o) negociation protocol to automagically set the best parameters for a given line: - negociateLinkForPort:(const char*) device; (o) in checkReceiver: // I might get rid of this if< // If we got here something HAS arrived at the port I'm not sure if the check is useful // On the other hand is this comparison significantly long? (o) archiving and NXTransport conformance yet to be implemented (o) should really add other initializers - initDevice:(const char*) device at:(int) speed withParity:(int) parity andMode:(int) mode; etc< (o) stop bits? (o) add support for the special characters structures and local mode word (o) many #import are probably missing (o) if the miscLockFile says it couldn't lock, I should check if the current lockfile is stalled or valid. (o) should write the PID in the lockfile. (o)- ( BOOL ) deviceIsAvailable: ( const char * )name should check if the device name is valid. (o) when changing the device of a connected object, the new device is automatically opened (o) when asked to changed its device name to an unavailable device, the object changes its device to NULL and reports that in the status word I think this should be changed (keep the same device?).
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.