Closed GoogleCodeExporter closed 9 years ago
Note that I've been thinking that the base system should implement a
#defaultPlatformAttributes method, so I wouldn't have to poke around in various
places to guess what the attributes should be ... same thing goes for the
version-specific attributes (like #gemstone3.x or squeak4.2 or #pharo1.3) since
I'd rather not have to ship a new version Metacello to do the additional tests
... don't know if I can get across the board adoption...
Original comment by henrichs...@gmail.com
on 7 Aug 2011 at 8:48
Tell us what would make your life easier. For me I would love to have a simple
class that avoid all the duplication :)
Original comment by stephane...@gmail.com
on 8 Aug 2011 at 7:19
http://code.google.com/p/pharo/issues/detail?id=4613 is open for collecting
input ... I can make a similar addition for GemStone ....
Original comment by henrichs...@gmail.com
on 9 Aug 2011 at 8:34
took care of both problems: extra checks for match before throwing an error and
use SmalltalkImage>>metacelloPlatformAttributes for attributes, if present
Metacello 1.0-beta.30 (dkh.627)
Original comment by henrichs...@gmail.com
on 8 Sep 2011 at 9:12
Issue 142 has been merged into this issue.
Original comment by henrichs...@gmail.com
on 18 Jan 2012 at 6:28
Original issue reported on code.google.com by
henrichs...@gmail.com
on 7 Aug 2011 at 8:42