Getting rid of select
|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
 |
Getting rid of select
by Eric Bezault
::
Rate this Message:
Hi Colin,
I can see that in classes XM_XSLT_GROUP_NODE_ITERATOR and XM_XSLT_SORTED_GROUP_NODE_ITERATOR you are using 'select'. Apart from UC_STRING, these are the only two occurrences of 'select' in Gobo. Right from the start I tried to avoid using 'select' because it was not working correctly when compiled with SmartEiffel. OK, we don't care about SmartEiffel anymore, but now there is a push from ECMA to get rid of 'select'. So I was wondering why you used 'select' in these classes. Was it just because the features involved were attributes and one cannot undefine an attribute (to have it merged with the version from the other inheritance branch)? If this is the reason, then there is a way to merge two attributes coming from two different parents. You just have to redefine this attribute in both inheritance branches: class C inherit A redefine attr end B redefine attr end feature attr: TYPE -- ... end -- Eric Bezault mailto:ericb@... http://www.gobosoft.com ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ gobo-eiffel-develop mailing list gobo-eiffel-develop@... https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop |
|
|
Re: Getting rid of select
by Colin Adams-3
::
Rate this Message:
I don't remember, but I suspect that must have been the reason.
2008/5/1 Eric Bezault <ericb@...>: > Hi Colin, > > I can see that in classes XM_XSLT_GROUP_NODE_ITERATOR and > XM_XSLT_SORTED_GROUP_NODE_ITERATOR you are using 'select'. > Apart from UC_STRING, these are the only two occurrences of > 'select' in Gobo. Right from the start I tried to avoid using > 'select' because it was not working correctly when compiled > with SmartEiffel. OK, we don't care about SmartEiffel anymore, > but now there is a push from ECMA to get rid of 'select'. > So I was wondering why you used 'select' in these classes. > Was it just because the features involved were attributes > and one cannot undefine an attribute (to have it merged with > the version from the other inheritance branch)? If this is > the reason, then there is a way to merge two attributes coming > from two different parents. You just have to redefine this > attribute in both inheritance branches: > > class C > inherit > A > redefine > attr > end > B > redefine > attr > end > feature > attr: TYPE > -- ... > end > > -- > Eric Bezault > mailto:ericb@... > http://www.gobosoft.com > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gobo-eiffel-develop mailing list > gobo-eiffel-develop@... > https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ gobo-eiffel-develop mailing list gobo-eiffel-develop@... https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop |
| Free Forum Powered by Nabble | Forum Help |