- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3523 in pharo: Nested comments

by pharo＠googlecode.com

Comment #6 on issue 3523 by stephane.ducasse: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 I was sure somebody would find the problem :). There was a lng thread a while ago in VW about that but now "* *" looks good to me because this is just a comment so :)

Jan. 11, 2011

Re: [Pharo-project] ZeroMQ, Mongrel2...

by StÃ©phane Ducasse

Thanks goran It would be good to structure a bit all these data. I hope that we will have a new squeaksource that helps us to get a better visibility for us but also from others Stef On Jan 11, 2011, at 9:51 PM, GÃ¶ran Krampe wrote: > Not at all the same thing as ZeroMQ but I did implement STOMP a while back: > > http://www.squeaksource.com/StompProtocol.html > > regards, GÃ¶ran >

Jan. 11, 2011

Re: [Pharo-project] [Vm-dev] Re: Waste of CPU Power by polling events?

by Igor Stasenko

On 11 January 2011 20:23, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > 2011/1/11 Levente Uzonyi <leves(a)elte.hu> >> >> >> On Tue, 11 Jan 2011, Eliot Miranda wrote: >> >> (Pine can't quote your mail, sorry.) >> >> "The problem with linux is that the pthreads implementation doesn't allow a normal user-level process to create high-priroity threads so that as >> soon as the Vm starts to spin doing some computation the heartbeat thread is shut-out and if the spinning computation only interrupted when a delay >> expires it'll never get interrupted because it is blocking the very thread that would signal the delay. Â So until linux's pthreads implementation >> supports multiple priorities we're stuck with hacks like the interval timer based itimer in the linux Cog VMs." >> >> What about keeping the priority of the heartbeat thread at user-level and decreasing the other VM threads' priority slighly? > > Linux doesn't allow more than /one/ thread priority for threads in a user-level process. Â So one /can't/ have multiple priorities. Â All threads run at the same priority. Â This is a horrible bug in the linux pthreads implementation but there it is. So, why not use signals & POSIX timer [1] for same purpose? Or do signals having other issues which even worse than using heartbeat process? [1] http://www.kernel.org/doc/man-pages/online/pages/man2/timer_create.2.html > best > Eliot >> >> Levente > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 11, 2011

Re: [Pharo-project] Issue 3531 in pharo: [FIX]ParseNodeEnumerator does not visits ivar nodes

by pharo＠googlecode.com

Comment #2 on issue 3531 by siguctua: [FIX]ParseNodeEnumerator does not visits ivar nodes http://code.google.com/p/pharo/issues/detail?id=3531 - added right changeset Attachments: ParseNodeEnumerator-fix-ivar-visiting.1.cs 902 bytes

Jan. 11, 2011

Re: [Pharo-project] ZeroMQ, Mongrel2...

by GÃ¶ran Krampe

Not at all the same thing as ZeroMQ but I did implement STOMP a while back: http://www.squeaksource.com/StompProtocol.html regards, GÃ¶ran

Jan. 11, 2011

Re: [Pharo-project] Issue 3531 in pharo: [FIX]ParseNodeEnumerator does not visits ivar nodes

by pharo＠googlecode.com

Comment #1 on issue 3531 by nicolas.cellier.aka.nice: [FIX]ParseNodeEnumerator does not visits ivar nodes http://code.google.com/p/pharo/issues/detail?id=3531 Hi Igor, sounds like the wrong .cs

Jan. 11, 2011

Re: [Pharo-project] PHP Fog ...

by csrabak＠bol.com.br

Geert, Even before we get into the sizing of market, we need to see if injecting Venture Capital into Pharo will do for the better or not... -- Cesar Rabak Em 11/01/2011 07:19, Geert Claes < geert.wl.claes(a)gmail.com > escreveu: I reckon a Smalltalk-type Heroku/PHP Fog (http://techcrunch.com/2011/01/10/php-fog-raises-1-8-million-to-be-the-herok…) would be nice :) Would there be a viable business opportunity there or is the market simply too small? -- View this message in context: http://forum.world.st/PHP-Fog-tp3208657p3208657.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 11, 2011

[Pharo-project] Issue 3531 in pharo: [FIX]ParseNodeEnumerator does not visits ivar nodes

by pharo＠googlecode.com

Status: Fixed Owner: siguctua CC: stephane.ducasse, marcus.denker, eliot.miranda Labels: Milestone-1.2 New issue 3531 by siguctua: [FIX]ParseNodeEnumerator does not visits ivar nodes http://code.google.com/p/pharo/issues/detail?id=3531 i found that enumerator does not does not visits the instance variable node: visitInstanceVariableNode: anInstanceVariableNode (self shouldVisit: anInstanceVariableNode) ifFalse: [^nil]. " theBlock value: anInstanceVariableNode. <<<< missing " ^super visitInstanceVariableNode: anInstanceVariableNode I thought that it was left on purpose, but Eliot confirmed that its a bug. The fix is in attachment. Attachments: CompilerParser-class-fix.1.cs 408 bytes

Jan. 11, 2011

Re: [Pharo-project] Issue 3523 in pharo: Nested comments

by csrabak＠bol.com.br

I hope this does look like nitpicking, but C comments are /* */ not */ /* HTH -- Cesar Rabak Em 10/01/2011 05:23, pharo(a)googlecode.com escreveu: Status: Accepted Owner: aplantec New issue 3523 by aplantec: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 Now let me open a big can of worms but we truly need it. When you write documentation (I did several experiments with Soup) the documentation in class comment is cool because you to not have to have " and " and '' ' ' '' '" everytimes you manipulate a string or a comment. Now you do not want to have huge class comments I would prefer to have a couple of methods and it does not work: you put back the crappy unnestable " ugly boring.... better not putting comments. So I would really like to have */ this is a nice nestable comment "hkjkhhkjh " 'hkjjkh' 1 + 2 */yet another comment: increbile this is a nested ones: yes you know Smalltalkers are discovering the world/* /* As you see stealing the C comment syntax is a plus because everybody knows it. I remember a discussion on VW about possible syntax to support that. Before replying to this point thing hard because we need that support.

Jan. 11, 2011

Re: [Pharo-project] [Vm-dev] Re: Waste of CPU Power by polling events?

by Eliot Miranda

2011/1/11 Levente Uzonyi <leves(a)elte.hu> > > On Tue, 11 Jan 2011, Eliot Miranda wrote: > > (Pine can't quote your mail, sorry.) > > "The problem with linux is that the pthreads implementation doesn't allow a > normal user-level process to create high-priroity threads so that as > soon as the Vm starts to spin doing some computation the heartbeat thread > is shut-out and if the spinning computation only interrupted when a delay > expires it'll never get interrupted because it is blocking the very thread > that would signal the delay. So until linux's pthreads implementation > supports multiple priorities we're stuck with hacks like the interval timer > based itimer in the linux Cog VMs." > > What about keeping the priority of the heartbeat thread at user-level and > decreasing the other VM threads' priority slighly? > Linux doesn't allow more than /one/ thread priority for threads in a user-level process. So one /can't/ have multiple priorities. All threads run at the same priority. This is a horrible bug in the linux pthreads implementation but there it is. best Eliot > > > Levente >

Jan. 11, 2011