[Seaside-dev] Issue 117 in seaside: rename #toString......... again

[codesite-noreply at google.com]

Issue 117: rename #toString......... again
http://code.google.com/p/seaside/issues/detail?id=117

Comment #4 by wembley.instantiations:
Niall and John did a quick examination of VW, the dialect that dislikes
Object>>asString.  The problem is a couple of methods on GenericException  
that do
not know whether an evaluable object (probably a block) has been passed in  
or a
String-like object.  Object already responds to value (thanks to the Squeak  
porting
layer) so they use whether the instance responds to asString to distinguish  
the two
classes of object.

This should be changed to eliminate respondsTo: in favour of isEvaluable or
similar.  Niall will raises this as a possible 7.7 fix;  for something as
fundamental as exceptions, it may not be a quick patch earlier but watch  
this space.

First cut summary, to be reviewed, is:
- endure another method name
- expect to rename back to asString when VW can endure that




-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings