January 2015 - Pharo-dev - lists.pharo.org

are senders and implementors broken in Pharo40?

by stepharo

When I do senders of buildFrom: I get nautilus pointing a class but not the method? No time to fix it but we should avoid to integrate enh that breaks the browser like that. Stef

Jan. 8, 2015

Re: [Pharo-dev] [ OT ] Je suis Charlie

by stepharo

tx! Education is the only way. > A couple of days ago, a French guy here in Buenos Aires was telling me > that France is not how it used to be, that a lot of violence is going > on... And I was refusing to believe him, given such a wonderful and > warming experience living in Lille. And then, this... But it is not > just France, it's > over the world, we live among a lot of violence and intolerance, and > we forget that all in all we are all people. > Or ar least, some tiny groups of people forget, and live in the belief > that they have the right to decide who deserves to live or not. > But as one of our presidents wrote (yes, in French): On ne tue pas les > idÃ©es. > > Trop triste. Je suis bouleversÃ©e. Toutes mes pensÃ©es vont aux amis en > France. > On est tous Charlie. > >

Jan. 8, 2015

Re: [Pharo-dev] using the command line to recompile a method that has a halt but shouldn't

by stepharo

Hi paul from a startup loop this is painful. Have a look at the explanation given some weeks ago by vincent blondeau. I will check this dependency because it smells strange to me. Stef Le 8/1/15 20:35, Paul DeBruicker a Ã©crit : > Without thinking about it too much I put a halt in RxParser>>#buildFrom: then saved & restarted the image. Now my image is in an infinite loop because buildFrom: is used in logging halts. > > > How can I recompile or revert #buildFrom: to the previous version? > > Thanks > > > A sample of the stack is: > > Halt > RxMatcher>>buildFrom: > RxMatcher>>initialize:ignoreCase: > RxMatcher class>>for:ignoreCase: > RxMatcher class>>for: > ByteString(String)>>asRegex > Path class>>absoluteWindowsPathRegex > Path class>>isAbsoluteWindowsPath: > Path class>>from:delimiter: > MacStore(FileSystemStore)>>pathFromString: > FileSystem>>pathFromString: > ByteString(String)>>asPathWith: > FileSystem>>pathFromObject: > FileSystem>>referenceTo: > ByteString(String)>>asFileReference > FileStream class>>fullName: > FileStream class>>fileNamed: > SmalltalkImage>>openLog > SmalltalkImage>>logDuring: in Block: [ ... > BlockClosure>>ensure: > SmalltalkImage>>logDuring: > SmalltalkImage>>logError:inContext: > StartupUIManager(CommandLineUIManager)>>quitFrom:withMessage: in Block: [ ... > BlockClosure>>ensure: > StartupUIManager(CommandLineUIManager)>>quitFrom:withMessage: > StartupUIManager(CommandLineUIManager)>>unhandledErrorDefaultAction: > Halt>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > >

Jan. 8, 2015

using the command line to recompile a method that has a halt but shouldn't

by Paul DeBruicker

Without thinking about it too much I put a halt in RxParser>>#buildFrom: then saved & restarted the image. Now my image is in an infinite loop because buildFrom: is used in logging halts. How can I recompile or revert #buildFrom: to the previous version? Thanks A sample of the stack is: Halt RxMatcher>>buildFrom: RxMatcher>>initialize:ignoreCase: RxMatcher class>>for:ignoreCase: RxMatcher class>>for: ByteString(String)>>asRegex Path class>>absoluteWindowsPathRegex Path class>>isAbsoluteWindowsPath: Path class>>from:delimiter: MacStore(FileSystemStore)>>pathFromString: FileSystem>>pathFromString: ByteString(String)>>asPathWith: FileSystem>>pathFromObject: FileSystem>>referenceTo: ByteString(String)>>asFileReference FileStream class>>fullName: FileStream class>>fileNamed: SmalltalkImage>>openLog SmalltalkImage>>logDuring: in Block: [ ... BlockClosure>>ensure: SmalltalkImage>>logDuring: SmalltalkImage>>logError:inContext: StartupUIManager(CommandLineUIManager)>>quitFrom:withMessage: in Block: [ ... BlockClosure>>ensure: StartupUIManager(CommandLineUIManager)>>quitFrom:withMessage: StartupUIManager(CommandLineUIManager)>>unhandledErrorDefaultAction: Halt>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal:

Jan. 8, 2015

Re: [Pharo-dev] The Smalltalk Revolution

by horrido

Yes, I posted to both Reddit and Hacker News simultaneously. Looks like it has a slower uptake at Hacker News: https://news.ycombinator.com/item?id=8856503 <https://news.ycombinator.com/item?id=8856503> Is it possible that I've finally succeeded in igniting a revolution? I feel like Che Guevara. sebastian(a)flowingconcept.com wrote > It was posted already on Hacker News or Reddit? > > If not, it sounds like is the right time to do that > > >> On Jan 8, 2015, at 5:03 PM, horrido < > horrido.hobbies@ > > wrote: >> >> WHOA! My article is *ON FIRE!* Seven hours into publication and it has >> achieved a staggering 2.7K views, 1.1K reads, and 9 recommendations. It's >> catching up to my best article ever, " The Case for Go Web Frameworks >> <https://medium.com/@richardeng/the-case-for-go-web-frameworks-a791fcd79d47 >> <https://medium.com/@richardeng/the-case-for-go-web-frameworks-a791fcd79d47>> >> ", which had 3.9K views and 2.4K reads. >> >> Who would've thought that Smalltalk would be such a hot topic?! I am >> truly >> flabbergasted. >> >> >> horrido wrote >>> In >> * >>> the 3 hours >> * >>> since this article was published at Medium, it has garnered >> * >>> 178 views >> * >>> and >> * >>> 96 reads >> * >>> , and counting! This makes it easily the most "hot" article I've ever >>> written. It is currently at the top of >>> Medium's front page <https://medium.com/> >>> which is reserved for "hot" or "trending" articles. >>> >>> Thanks to everyone! >>> horrido wrote >>>> https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51 >>>> <https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51> >>>> >>>> I welcome your comments. It's not too late to edit the piece. >>>> >>>> Thanks. >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798436.html >> <http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798436.html> >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com <http://nabble.com/>. -- View this message in context: http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798440.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 8, 2015

Re: [Pharo-dev] The Smalltalk Revolution

by horrido

Funnily enough, one guy commented: 'The hype of the article is grating ("Smalltalk is the future of software development"? Really?' Yes, really! That's the point of Smalltalk Renaissance: to build type, to create a brand, to draw attention. Looks like it's succeeding! philippeback wrote > Added some answers over there.â > > Phil -- View this message in context: http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798439.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 8, 2015

Re: [Pharo-dev] The Smalltalk Revolution

by Sebastian Sastre

It was posted already on Hacker News or Reddit? If not, it sounds like is the right time to do that > On Jan 8, 2015, at 5:03 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > > WHOA! My article is *ON FIRE!* Seven hours into publication and it has > achieved a staggering 2.7K views, 1.1K reads, and 9 recommendations. It's > catching up to my best article ever, " The Case for Go Web Frameworks > <https://medium.com/@richardeng/the-case-for-go-web-frameworks-a791fcd79d47 <https://medium.com/@richardeng/the-case-for-go-web-frameworks-a791fcd79d47>> > ", which had 3.9K views and 2.4K reads. > > Who would've thought that Smalltalk would be such a hot topic?! I am truly > flabbergasted. > > > horrido wrote >> In > * >> the 3 hours > * >> since this article was published at Medium, it has garnered > * >> 178 views > * >> and > * >> 96 reads > * >> , and counting! This makes it easily the most "hot" article I've ever >> written. It is currently at the top of >> Medium's front page <https://medium.com/> >> which is reserved for "hot" or "trending" articles. >> >> Thanks to everyone! >> horrido wrote >>> https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51 >>> <https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51> >>> >>> I welcome your comments. It's not too late to edit the piece. >>> >>> Thanks. > > > > > > -- > View this message in context: http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798436.html <http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798436.html> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com <http://nabble.com/>.

Jan. 8, 2015

Re: [Pharo-dev] The Smalltalk Revolution

by horrido

WHOA! My article is *ON FIRE!* Seven hours into publication and it has achieved a staggering 2.7K views, 1.1K reads, and 9 recommendations. It's catching up to my best article ever, " The Case for Go Web Frameworks <https://medium.com/@richardeng/the-case-for-go-web-frameworks-a791fcd79d47> ", which had 3.9K views and 2.4K reads. Who would've thought that Smalltalk would be such a hot topic?! I am truly flabbergasted. horrido wrote > In * > the 3 hours * > since this article was published at Medium, it has garnered * > 178 views * > and * > 96 reads * > , and counting! This makes it easily the most "hot" article I've ever > written. It is currently at the top of > Medium's front page <https://medium.com/> > which is reserved for "hot" or "trending" articles. > > Thanks to everyone! > horrido wrote >> https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51 >> <https://medium.com/@richardeng/the-smalltalk-revolution-ee245c281f51> >> >> I welcome your comments. It's not too late to edit the piece. >> >> Thanks. -- View this message in context: http://forum.world.st/The-Smalltalk-Revolution-tp4798320p4798436.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 8, 2015

Re: [Pharo-dev] The Smalltalk Revolution

by phil＠highoctane.be

Added some answers over there.â Phil

Jan. 8, 2015

[Pharo4] Failing tests in Pharo4

by Marcus Denker

Hi, We have just 4 failing tests left in Pharo4: ClassTest>>#testClassRespectsPolymorphismWithTrait https://pharo.fogbugz.com/f/cases/14608 SHParserST80Test>>#testNumbers https://pharo.fogbugz.com/f/cases/14590 ObsoleteTest>>#testFixObsoleteSharedPools https://pharo.fogbugz.com/f/cases/14165 ReleaseTest>>#testObsoleteClasses https://pharo.fogbugz.com/f/cases/14470

Jan. 8, 2015