Check the chapter Anne and JC wrote on pharoinprogress.
We discussed a lot about RB because the unification does not identify
the subtree people think about.
I will let Camille and JC comment on it.
What we saw is that we should try something because they are too many
edge corner.
Le 5/7/15
Would be possible for STON to report context for error?
For example
STON fromString: '[
"first",
"second",
]'
reports "At character 23: invalid input" which is not very useful
especially in longer strings.
(at: 23 is actually Character cr)
Maybe better would be something like
'At character 23:
How come this passes?
STON fromString: '{
"a": "b"
}wtf",
"x": "y"
'.
The result is dictionary "a" -> "b".
I would expect for it to die on parse error.
Peter
Le 04/07/2015 23:06, stepharo a écrit :
>
>>> For the information we are working on touch and OSWindow improvements.
>>> Alain is imporving Bloc the future graphic layer of Pharo, people from
>>> bern are working on new widgets.
>>> We are working on cleaning widgets. Now we also accept help.
>>>
>
Hi Peter,
> On 05 Jul 2015, at 14:36, Peter Uhnák wrote:
>
> How come this passes?
>
> STON fromString: '{
> "a": "b"
> }wtf",
> "x": "y"
> '.
>
> The result is dictionary "a" -> "b".
>
> I would expect for it to die on parse error.
>
> Peter
The reason this does not fail is bec
Ok but how does the parser knows whether the input is multiexpression or an
error?
I mean it stops parsing in the middle of the string which seems really
weird to me.
Peter
On Sun, Jul 5, 2015 at 3:28 PM, Sven Van Caekenberghe wrote:
> Hi Peter,
>
> > On 05 Jul 2015, at 14:36, Peter Uhnák wrot
Le 05/07/2015 12:41, stepharo a écrit :
Check the chapter Anne and JC wrote on pharoinprogress.
We discussed a lot about RB because the unification does not identify
the subtree people think about.
I will let Camille and JC comment on it.
What we saw is that we should try something because they a
The user/caller decides what it expects from the input and how to deal with
exceptions.
For example, here is how to read multiple expression until EOF
Array streamContents: [ :out |
[ reader atEnd ] whileFalse: [ out nextPut: reader next ] ]
I think the current design is the both simple and f
> On 05 Jul 2015, at 14:19, Peter Uhnák wrote:
>
> Would be possible for STON to report context for error?
> For example
>
> STON fromString: '[
> "first",
> "second",
> ]'
>
> reports "At character 23: invalid input" which is not very useful especially
> in longer strings.
> (at:
For the information we are working on touch and OSWindow improvements.
Alain is imporving Bloc the future graphic layer of Pharo, people from
bern are working on new widgets.
We are working on cleaning widgets. Now we also accept help.
Stef
Sure I know. The constituting parts does not make the
Hello,
can anyone summarize the situation of Squeak/Pharo under Raspberry PI at
the moment ?
What platform/version is working, which vm should be used and it should
be useable ... what is the difference of SPUR here etc
Thanks,
--
Marten Feldtmann
--- Begin Message ---
> I'm not sure that we need a DSL.
I’m not sure that we don’t need a DSL :)
Spec is a kind of dsl and the idea is cool.
>> This is a point that particularly interests me, especially regarding
>> declarative syntax.
>> Yes, but unfortunately not in 3 month (for my part)...
>
Hi Marten,
Currently I'm using this this vm from here
http://www.mirandabanda.org/files/Cog/VM/VM.r3395/cogspurlinuxhtARM-15.26.3395.tgz
with the latest Pharo 5 spur image from here
http://files.pharo.org/image/50/latest-spur32.zip
As far as I know, spur is a new memory manager but I'm not fa
2015-06-18 14:49 GMT+02:00 Matthieu Lacaton :
> Hello,
>
> I wanted to use Athens API to define a radial gradient and I saw that the
> class RadialGradientPaint only had one radius as instance variable and it
> seemed to me it was passed as the end radius while the start radius was set
> to 0.
> D
14 matches
Mail list logo
