[Pharo-project] start thinking on summer release of Pharo 1.4

Sean P. DeNigris sean at clipperadams.com
Fri Jun 15 14:49:38 EDT 2012


Schwab,Wilhelm K wrote
> 
> My gripe is... that configs... work (very) differently over time
> 
With the current evolution of Metacello, this should not be the case. Done
right, what a config loads can be 100% static and repeatable. If you load a
literal version (e.g. '1.4'), which loads literal versions of dependent
projects (which they should unless there is a reason not to, e.g. a loose
dependency like Seaside on OB), which load literal versions all the way
down, it will do the same thing today, tomorrow, and ten years from now.

The only hill to climb now is getting the word out about Metacello
conventions/best practices.


Schwab,Wilhelm K wrote
> 
> If pre-loading, how about FFI?
> 
I think "easily loadable" is the correct state, not included by default.

--
View this message in context: http://forum.world.st/start-thinking-on-summer-release-of-Pharo-1-4-tp4634589p4635009.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.




More information about the Pharo-dev mailing list