Bob Tarling wrote:
There are deprecated methods in Profile and yet we have not had a
stable release yet with that class. Do we really need to deprecate
under those circumstances.
Yes, I think that the use of deprecated was intended to avoid disruption
of development code. AFAIK only the C++ module outside of the core is
using this API, so, +1 to remove these deprecated methods and classes.
Maybe there is a some other last minute tidying up we can do now.
Would it be worth making Profile an interface rather than a class?
Bob.
I thought about that, but, at the time I was looking at different
refactorings. I would simply refactor Profile class into Profile
interface + AbstractProfile class.
Regards,
Luis
PS: there is issue 4885 for refactoring the profile sub-system.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
