Kees Jongenburger wrote: > > I think as such, the PageContext will start with 2 deprecated members and > > perhaps 2 deprecated methods (and do'nt see the point of resetting req and > > res). I think it is odd to have a new class with deprecated stuff in it, but > > well, if at least it is clear that it _is_ deprecated, I'm not against that. > So we are replacing deprecated code with deprecated code. Well at > least we will know > the old code will need changes and the new code shouldn't use it. > whats the point?
I think the only point is that you can relatively easily move scanpage to the scan-application then. PageContext is considerably easier to maintain, and there is a good chance that you can fix builders and modules using scanpage by s/scanpage/PageContext/g. Making a really likeable sollution, (e.g. with Functions or so), would require much more thinking and coding to fix such things. So, I think PageContext is perhaps justifiable as a migration utility, but still, it should be deprecated itself then, i.e. when there is an alternative.. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
