-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm one to view "deprecate always" if there's been a release - buggy or not. Once it's out there, someone will use it and either find it works perfectly for them, work around the issues, or abandon their use of it. Immediate removal will mean the "abandon their use of it" won't be the option chosen. :-) If the buggy interface is introduced and fixed within a release cycle - rip the band aid off really fast.
Appreciate the work for a patch. Hopefully this will ease a vote for release. [and if my access comes in time I'll be glad to step in on it to ease 4.1 resources] Brian Fernando Padilla wrote: > Sorry. I feel bad for the original poster, I'm the one that submitted > the patch thinking that FormSupport was an internal class only used by > Form, so I guess I'm the root cause for David's bad day at work.. I know > how I hate it when the rug gets pulled out from under me without > expecting it. > > So I probably should have left the old signature there and marked it > deprecated.. shrug, relatively easy thing to do.. > > But the old signature was buggy.. so should we be supporting a buggy > interface.. or just pull the bandaid really fast and deal with the pain > as soon as possible.. open ended philosophical discusson.. but yes this > was a tiny minor release, it shouldn't have given anyone any source of > headaches.. sorry.. I'll see if I can build a patch to expose the old > signature deprecated. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFENfLZaCoPKRow/gARAupjAJ92uabOsdULKzwtQW4w7KpgTAijqQCgl1Ou Pawm/h+Pi1rMaFLVHsQk/pI= =seMv -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
