2009/6/17 Gabriel Cotelli <g.cotelli@gmail.com>
This is the list of methods missing in BlockClosure but covered by the BlockContextTest:
- copyStack - bottomContext - findContextSuchThat: - tempNamed: - tempNamed:put:
I don't known if has sense to implement that...
I have no idea, but in my image (Pharo 10342) I see several senders: * copyStack Process>>copyStack * bottomContext ContextPart>>insertSender: Process>>terminate * findContextSuchThat: BlockContext>>activeHome ContextPart>>buttomContext ContextPart>>findSimilarSender ContextPart>>hasContext: ContextPart>>secondFromButtom Exception>>signalerContext MethodContext>>activeHome MethodContext>>activeOuterContext Process>>calleeOf: * tempNamed: * tempNamed:put: Mariano
On Wed, Jun 17, 2009 at 4:28 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi Gabriel
Could you post a list of these methods? Probably it makes sense to copy some of them over to BlockClosure to preserve compatibility for external clients (we had this before, e.g., #argumentCount, IIRC which is used by GLORP or Seaside).
Else these tests can be removed.
Adrian
On Jun 17, 2009, at 02:28 , Gabriel Cotelli wrote:
Hi,
I'm looking the failing tests... some tests defined in BlockContextTest relies on behavior not implemented in BlockClosure (but implemented in the old BlockContext)...
If the only senders of this methods are in this test cases can I remove them?
If I don't miss anything BlockContext should not be used anymore...
Waiting for your comments... Gabriel _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project