Re: [Pharo-dev] Future of Spec

2014-08-30 Thread Martin Saurer
It's already planned ;-) Martin > as far as I understand J is an APL like language so I was wondering > with you do not have J binding inside pharo :) ? > and script J from there? > > Stef

Re: [Pharo-dev] background color text attribute?

2014-08-30 Thread stepharo
hi doru do you mean like when we select the code? Stef On 28/8/14 07:00, Tudor Girba wrote: Hi, Does any of you know if there is a way to add a background color to a piece of text? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Re: [Pharo-dev] Anonymous classes in Pharo 3 - must be instances of Class, not Behavior

2014-08-30 Thread stepharo
On 29/8/14 14:01, Camille Teruel wrote: On 29 août 2014, at 13:38, Oscar Nierstrasz wrote: Following up: Behavior new compile: 't ^ true’ fails since #compile: is defined in TBehavior and depends on #basicLocalSelectors which is defined only in Class, MetaClass and TraitBehavior.

Re: [Pharo-dev] >>#next: SocketStream and other oddities

2014-08-30 Thread Sven Van Caekenberghe
Holger, You are right and wrong ;-) SocketStream is what it is, it is far from perfect, but it works and had been working for a very long time. There are alternatives. The well documented contract of SocketStream #next: and all its variants up to #readInto:startingAt:count: states and explains

Re: [Pharo-dev] >>#next: SocketStream and other oddities

2014-08-30 Thread Ben Coman
I'm not an expert on networking stuff, but I'll try (and if I'm wrong I'll learn something new)... Holger Hans Peter Freyther wrote: Classic ReadStream in Pharo3.0 #[] readStream next: 2 => #[] SocketStream: 1.) Start something that listens to 12345 $ nc -l -p 12345 2.) In Pharo do

Re: [Pharo-dev] >>#next: SocketStream and other oddities

2014-08-30 Thread Holger Hans Peter Freyther
On Sat, Aug 30, 2014 at 09:19:49AM +0200, stepharo wrote: > Hi holger Hi! thanks for the answer. > I got confused. sorry about that. > There is a problem with next: not raising error? Classic ReadStream in Pharo3.0 #[] readStream next: 2 => #[] SocketStream: 1.) Start something that l

Re: [Pharo-dev] ObjectLiterals thoughts....

2014-08-30 Thread stepharo
For now parsetime as #() Are you considering a form of compile-time expression or quasi-quotes? On 29 August 2014 11:35, stepharo wrote: Hi guys we are looking at STON and ObjectLiterals with Christophe and for handling metadata. And I was brainstorming I was wondering if it would be po

Re: [Pharo-dev] ObjectLiterals thoughts....

2014-08-30 Thread stepharo
On 29/8/14 11:56, Sven Van Caekenberghe wrote: Hi, I had a quick look at the ObjectLiterals project - I must admit that I forgot most about it ;-) me too :) Christophe was patching STON to make it less verbose when I remembered that igor sent some ideas around. Now that I see it again, on

Re: [Pharo-dev] ObjectLiterals thoughts....

2014-08-30 Thread stepharo
Hey! Just for some "food for thought", you may want to read the parts under heading "Literal Smalltalk arrays" and the section following - "Sidestory: Adding literal Dictionaries to Smalltalk?" ...at: http://goran.krampe.se/2012/05/08/literal-arrays-vs-json-vs-ston-vs-tirade/ regards, Göra

Re: [Pharo-dev] ObjectLiterals thoughts....

2014-08-30 Thread stepharo
do you know if amber has { } because ideally I would love to have something like #() literl array ##()dynamic array why not :) #{} literal dictionary ##{} dynamic literal dictionary On 29/8/14 12:53, Göran Krampe wrote: Hey! Just for some "food for thought", you may want

Re: [Pharo-dev] ObjectLiterals thoughts....

2014-08-30 Thread stepharo
**thanks** I will reread it and add it to my folder. because one day I would love to have literal dictionary syntax and (I think that this is a pity that { } is already use for dynamic arrays. Stf On 29/8/14 12:53, Göran Krampe wrote: Hey! Just for some "food for thought", you may want to r

Re: [Pharo-dev] >>#next: SocketStream and other oddities

2014-08-30 Thread stepharo
Hi holger I got confused. There is a problem with next: not raising error? Stef On 29/8/14 09:16, Holger Hans Peter Freyther wrote: Hi, while writing some SMS PDU parsing code I stumbled across an "oddity" I have not seen with GNU Smalltalk. When calling the #next: selector on a ReadStream

Re: [Pharo-dev] Future of Spec

2014-08-30 Thread stepharo
as far as I understand J is an APL like language so I was wondering with you do not have J binding inside pharo :) ? and script J from there? Stef On 29/8/14 21:15, Martin Saurer wrote: Dear Stef, Dear Pharo Community, Many thanks for answering my question about the future of Spec. What I ha