On Friday, 19. August 2005 14:41, Christopher H. Laco wrote: > Jörg Walter wrote: > [snip] > > > So my question is: Would you be affected by this? How do you think about > > the problem? Would you prefer getting the old (less flexible/dwimmy) > > behaviour instead?
> But, had I used SimpleTaglib, me reaction to an incompatable new version > is based on one other piece of information: How compatable is AxKit 1.7 > compared to 1.6? > > If there were other sweeping changes, I would just update my stuff and > set 1.7 as a PREREQ. But if AxKit 1.7 is quite compatable with 1.6, then > I think and imcompatable SimpleTaglib is a bad thing. Well, now that you mention it, there was a grave (and unfortunately unavoidable) change which already massively broke compatibility. OTOH, many people use CVS checkouts, these people would not encounter any significant change. Also, keep in mind that several things have to happen for this bug to show up, and that taglibs are easily fixed. We're talking about changing one line of affected tags, and only few tags are affected. It's really a mess, since there are so many "if's" and special cases. I'd love to do what I should have done in the first place, and then forget it all. > With that said though, AxKit->VERSION is your friend. I assume that it's > possible to change one's taglib to work with both 1.7 AND 1.6 AxKit > installs? That would perfectly possible, and no need for AxKit->VERSION. The fix would be to replace code like this: return @result; with either: return $result[0]; (if @result only has one element and you were just being lazy), or return ([EMAIL PROTECTED]:$result[0]); XSP pages won't have to be touched unless we keep the current situation. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
