From: Stephen D. <sd...@gm...> - 2005-02-21 23:21:22
|
What's the story on backwards compatibility? I'd say we should try to maintain backwards compatibility where ever possible, and examine it on a case-by-case basis. So here's the case I'm thinking of: I created some infrastructure to help write C functions which take Tcl callbacks. The structure which gets passed around looks like this: typedef struct Ns_TclCallback { char *server; char *script; char *scriptarg; union { int intValue; void *ptrValue; } data; } Ns_TclCallback; That ugly data union is to support ns_register_proc and friends which take a 'conn' argument. The conn arg is no longer used and hasn't been since the server was released as open source. It's only there for backwards compatibility. So my question is, would anyone be upset if I removed support for passing around a fake 'conn' in functions like ns_register_proc, ns_conn, etc.? I seem to remember it's removal was mentioned on the other list some time ago, and it certainly makes the docs hard to read. |