Camillo Bruni-3 wrote >>> OSProcess should load fine and without legacy when 2.0 is released > I think once 2.0 is declared stable someone will take care of OSProcess.
I opened an issue... >From http://code.google.com/p/pharo/issues/detail?id=7281 : > I realize this is not a problem with Pharo itself, but OSProcess is > extremely important and we should track it to make sure it gets loadable > into 2.0. > > I'll email Dave and see what we can come up with... > > Pharo2.0a > Latest update: #20476 > > UndefinedObject(Object)>>doesNotUnderstand: #wait > UnixOSProcessAccessor>>grimReaperProcess in Block: [[event wait.... > BlockClosure>>newProcess in Block: [self value.... > > > At least one problem seems to be updating for FileSystem. > Also, deprecation warnings for OSPlatform class>>osVersion -- View this message in context: http://forum.world.st/The-monkey-is-back-in-town-tp4658091p4663955.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
