On Wed, Feb 27, 2019, 21:50 K K Subbu wrote:
>
>
> On 28/02/19 5:23 AM, Richard O'Keefe wrote:
>
> > It is surprisingly hard to keep categories consistent. If there is
> > a way to say "here I am browsing method M in category G of class C,
> > is there an ancestor of C that puts the selector of
On 28/02/19 5:23 AM, Richard O'Keefe wrote:
It is surprisingly hard to keep categories consistent. If there is
a way to say "here I am browsing method M in category G of class C,
is there an ancestor of C that puts the selector of M in a different
category?" I would love to know it. (Adding
If numeric keys are silently written as strings when generating
JSON, you can get JSON that is technically legal but practically
ambiguous. Start with the obvious:
(Dictionary new: 2) at: 1 put true; at: '1' put false; asJson
=> {"1": true, "1": false}.
More subtly,
d := Dictionary new: 2.
Esteban,
You are right !, the client is the culprint :)
Regards,
bruno
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
In my own Smalltalk, a string understands a little over two thousand
selectors, of which about 440 are specific to strings, the others
being shared by other sequences. That's quite a lot to search through.
As it happens, I *do* have a 'searching' category and the
#findString:[startingAt:][ignoring
I can't speak for Teapot, but I can tell you that the extra "body"
container object is not standard for JSON/REST API's.
Are you certain that it isn't the client who's adding such container
to the request?
Regards,
Esteban A. Maringolo
El mié., 27 feb. 2019 a las 18:56, BrunoBB () escribió:
>
Hi,
Using Teapot (which uses Zinc) i found something i do not know if it is a
standard or done on purpose or a bug.
A Teapot service (POST) accept a JSON entry. In the client the 'body' is set
with the JSON.
In the server the ZnRequest contents insert a JSON node 'body' to the
original JSON.
Th
Hi,
I have a build script too to build the drgeo bundle from scratch [1], I
will take a look yours to add up.
In the mean time I built a new mac os bundle with your info.plist.
I tested it on a mac, but without privilege to move it to the
Applications location. After downloading it to the Deskto
Thank you guys for the energy you put into this :-)
Noury
> On 26 Feb 2019, at 12:56, Serge Stinckwich wrote:
>
> Dear all,
>
> Pharo Consortium has been selected this year as a Google Summer of Code 2019
> mentor organization. This is the first time since 2017.
>
> I would like to thank oth
Hi Sven,
Excellent !!! That exactly what i want.
As an excuse i will say i'm one day old with NeoJSON :)
mapping decoder: [:x | ] plus #atPath: made my day !
Thanks very much for you clear response.
regards,
bruno
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
No - my point is, why are the basics for reasonable testing not in the image?
Such that tests are easy, and a joy to write where failures are obvious when
they occur.
We seem to have 2 extremes - assert:equals: does a lovely job of showing what
it expects and you got with a nice diff view (that
11 matches
Mail list logo
