Of you load the JSON package from Squeaksource
(http://www.squeaksource.com/JSON.html)
You can do a
JSON render: {
'track' -> 'pharo'.
'language' -> 'smalltalk'.
'exercises' -> {
'slug' -> 'hello'.
'id' -> 55.
'topics' -> #('a' 'b' 'c') }
}
and get a Json string or add e
Richard Sargent wrote
> As an aside, this is the kind of information that should be in a method's
> comment. Rationale and explanation, rather than what it does.
Yes!!!
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Hi,
I did some progress on the Dr.Geo bundle for OS X.
The Mac admin of my school told me to download from Safari and
authorized the drgeo.eu web site (not sure what this exactly does), then
we installed the DrGeo.app at the Application location.
DrGeo started fine but emit a startup error at th
Hey Ben,
I leave it with this answer, as you suggested, thank you for picking up
the ball!
First, I admit again, I have thought about it one whole day, if and how
I should do this "intervention", which is absolutly not my usual style,
but I decided for myself, to be intentionally blunt, provoc
Hey - sometimes these more philosophical conversations do amount to something.
I will propose to gene changes and submit a pr - as after all, Pharo is ours
and pointing someone to #downTo: or #upTo: would be very rewarding (and for
Richard - #to: would remain the same so everyone wins)
Tim
Sen
On Fri, Mar 1, 2019 at 12:02 PM Sven Van Caekenberghe wrote:
> Ah, it is an optimisation: if the first #== fails, but the argument is
> also a Symbol, then that means the are different for sure, so false is
> returned early, instead of failing in super's #= after that.
>
> And with ByteSymbol and
Ah, it is an optimisation: if the first #== fails, but the argument is also a
Symbol, then that means the are different for sure, so false is returned early,
instead of failing in super's #= after that.
And with ByteSymbol and WideSymbol, although they are exclusive (can never be
equal), they c
Is it consistent with the definition of #= in String such that
'aSymbol = aString' iff 'aString = aSymbol'?
Sorry, I don't have an image at hand.
Am 1. März 2019 18:40:11 MEZ schrieb Sven Van Caekenberghe :
>Why ? Please explain ...
>
>> On 1 Mar 2019, at 18:02, David T. Lewis wrote:
>>
>> On F
On 01/03/19 5:35 PM, Sven Van Caekenberghe wrote:
I like this too.
Why would this not happen ? It is just one selector more.
I think the only possible issue is that #to:do: is known by the
compiler, which makes it faster than any other iteration, even do: -
there is always a tradeoff between re
Why ? Please explain ...
> On 1 Mar 2019, at 18:02, David T. Lewis wrote:
>
> On Fri, Mar 01, 2019 at 05:18:27PM +0100, Sven Van Caekenberghe wrote:
>>
>>
>>> On 1 Mar 2019, at 17:08, Petr Fischer via Pharo-users
>>> wrote:
>>>
>>>
>>> From: Petr Fischer
>>> Subject: Symbol equality metho
Obviously its good to be circumspect at such an earlier stage,
but I can imagine a few "good" editors who publishing a book would really
lend some legitimacy and exposure to Pharo.
That would be overall beneficial even if the book is not free.
Stef, I am interested to know more.
cheers -ben
On F
Hi Michael,
Thanks for your thoughtful followup.
On Fri, 1 Mar 2019 at 19:59, Michael Zeder wrote:
>
> I have carefully thought about, if I should really go publicly against one
> person within the community, and to start this "tirade", including the
> possibility that this causes an escalation
On Fri, Mar 01, 2019 at 05:18:27PM +0100, Sven Van Caekenberghe wrote:
>
>
> > On 1 Mar 2019, at 17:08, Petr Fischer via Pharo-users
> > wrote:
> >
> >
> > From: Petr Fischer
> > Subject: Symbol equality method #= - weird condition in the Pharo sourcecode
> > Date: 1 March 2019 at 17:08:03 G
--- Begin Message ---
Issue submitted:
https://github.com/pharo-project/pharo/issues/2744
pf
> > On 1 Mar 2019, at 17:08, Petr Fischer via Pharo-users
> > wrote:
> >
> >
> > From: Petr Fischer
> > Subject: Symbol equality method #= - weird condition in the Pharo sourcecode
> > Date: 1 March
> On 1 Mar 2019, at 17:08, Petr Fischer via Pharo-users
> wrote:
>
>
> From: Petr Fischer
> Subject: Symbol equality method #= - weird condition in the Pharo sourcecode
> Date: 1 March 2019 at 17:08:03 GMT+1
> To: pharo-users@lists.pharo.org
>
>
> Hello, this is Symbol equality method in
--- Begin Message ---
Hello, this is Symbol equality method in Pharo:
1: = aSymbol
2: "Compare the receiver and aSymbol."
3: self == aSymbol ifTrue: [^ true].
4: self class == aSymbol class ifTrue: [^ false].
5: "Use String comparison otherwise"
6: ^ super = aSymbol
Look
What's missing is a "map" syntax. :)
#{
'track' -> 'pharo'.
'language' -> 'smalltalk'.
'exercises' -> #{
'slug' -> 'hello'.
'id' -> 55.
'topics' -> #('a' 'b' 'c') }
}
The #{ } would be a mix of the existing { } construct, but somehow
enforcing that elements return "associatio
> On 1 Mar 2019, at 12:32, Tim Mackinnon wrote:
>
>
>
>> On 1 Mar 2019, at 10:35, Sven Van Caekenberghe wrote:
>>
>> Forget about the way you are trying to implement it, to what would
>>
>> { #key->#value. 1. true }
>>
>> be rendered in JSON ?
>>
>> { "key":"value", 1, true }
>>
>>
> On 1 Mar 2019, at 12:22, Tim Mackinnon wrote:
>
> Actually thats quite a good suggestion - it probably should have been:
>
> #upTo:
> #downTo:
> #to:by:
>
> In the first place (but I’m guessing this change will never happen)
I like this too.
Why would this not happen ? It is just one sel
@Esteban: Thanks for your balanced answer. got it. But I get back to
the point of "silencing/ban" (which is not my suggestion).
@Eduardo: Right, sorry, this should have been more clearly (and I did
not want to be condescending towards newcomers). Soft skills and people
who create articles, tut
> On 1 Mar 2019, at 10:35, Sven Van Caekenberghe wrote:
>
> Forget about the way you are trying to implement it, to what would
>
> { #key->#value. 1. true }
>
> be rendered in JSON ?
>
> { "key":"value", 1, true }
>
> or
>
> [ "key":"value", 1, true ]
>
> Both are illegal JSON.
You
Actually thats quite a good suggestion - it probably should have been:
#upTo:
#downTo:
#to:by:
In the first place (but I’m guessing this change will never happen)
> On 1 Mar 2019, at 05:35, K K Subbu wrote:
>
> On 28/02/19 6:33 PM, Tim Mackinnon wrote:
>> So I would expect “1 to: 0” to see:
> On 28 Feb 2019, at 22:35, Tim Mackinnon wrote:
>
> Sven- thinking a bit more
>
>> On 28 Feb 2019, at 13:59, Sven Van Caekenberghe wrote:
>>
>> This is wrong !!
>>
>> Think about it, what would then happen with a mixed list ?
>>
>> { #key->#value. 1. true }
>>
>> That would generate inv
I would use any of the following:
ex := {
#track->#pharo.
#language->#smalltalk.
#exercises->{
#slug->'hello'.
#id->55.
#topics->#('a' 'b' 'c') } asDictionary } asDictionary.
ex := {
#track->#pharo.
#language->#smalltalk.
#exercises->({
#slug->'hello'.
#id->55.
24 matches
Mail list logo
