[MTOS-dev] Circular reference issue

[Byrne Reese]

The circular reference issue was not closed - the fix would substantially
delay MT4.1, so we are evaluating other ways to get the fix out to the
community. 

There will be fix, that is for sure, and it will be in MTOS of course. Just
not in 4.1.

It pains me to say.


On 1/18/08 2:09 PM, "Timothy Appnel" <tim at appnel.com> wrote:

> On 1/16/08, Hirotaka Ogawa <hirotaka.ogawa at gmail.com> wrote:
>> I agree with this suggestion.  In case Six Apart people employ weak
>> references, it is convenient to encapsulate "weaken codes" into
>> constructors and/or setter methods.
> 
> RC1 was released with all known issues meant to be resolved being
> taken care of so this is less of an issue for now.
> 
> Reading what you found in MT::Request I can see how other nodes would
> remain. I'm thinking that a standardize method for managing the
> caching of tokens is needed. Like Hirotaka suggests implementing a
> constructor would also be beneficial to managing this sort of thing in
> the feature.
> 
> I can't see hunting all of these instances down individually without
> these changes as they are likely to crop up again.
> 
> I still think the compile method could use an overhaul, but one battle
> at a time. We've yet to hear a think about our conversation here from
> the Six Apart engineers leading all of this work.
> 
> <tim/>