Re: [Pharo-users] Macros?

I've been reconstructing an old programming language. It originally had a very simple but awkward macro facility: if an identifier was declared as a macro, whenever it was called, it could inspect/consume as much of the remaining tokens as it wished and could splice other tokens in. On top of

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

Herbert Vojčík ​wrote " it is already part of the spec a few years already that enumeration on the object keys MUST respect the order in which keys were created". I quoted two specs: json.org and the ECMA one. The current RFC for JSON is, I believe, RFC 8259, which says JSON parsing

Re: [Pharo-users] Macros?

On Fri, May 25, 2018 at 10:12 AM, Ben Coman wrote: > > > On 25 May 2018 at 21:22, Debiller 777 wrote: >> >> Well, I've already asked about adding new literals to pharo or Smalltalk >> in general, however this time I have a better idea: >> macros. Can they be added? Because if I understand

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

Norbert Hartl wrote on 11. 6. 2018 23:38: Am 11.06.2018 um 16:48 schrieb Richard O'Keefe >: I'm really baffled here. Look at the definition at json.org . ​An object is an UNORDERED set of name/value pairs. Or look at ECMA-404, which

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.0

On Mon, Jun 11, 2018 at 7:23 PM, Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > Hi Guille, > > Thank you for the update. > Can this be installed in Pharo 6.1? How? > This is already in latest Pharo build. If you want to try it in a Pharo 6.1 (I recommend to do it in a clean image),

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.0

> > tag support, a new credential manager to manage keys and passwords per > host or repository Thank you! I'm looking forward to playing with this next week. (and reporting issues :)) Peter On Mon, Jun 11, 2018 at 7:23 PM, Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > Hi Guille,

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.0

Hi Guille, Thank you for the update. Can this be installed in Pharo 6.1? How? It was tested on Windows? Cheers, Hernán 2018-06-11 14:04 GMT-03:00 Guillermo Polito : > Time for the weekly Iceberg update. > Thanks to all brave users, issue reporters and contributors :). > > Key changes: we have

[Pharo-users] [Ann] Iceberg v1.1.0

Time for the weekly Iceberg update. Thanks to all brave users, issue reporters and contributors :). Key changes: we have introduced some tag support, a new credential manager to manage keys and passwords per host or repository, a new version of tonel, and made a first step towards a simplified

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

I'm really baffled here. Look at the definition at json.org. ​An object is an UNORDERED set of name/value pairs. Or look at ECMA-404, which json.org points to. The JSON syntax does not impose any restrictions on the strings used as names ... and DOES NOT ASSIGN ANY SIGNIFICANCE

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

Yes i was a bit nervous about the ordering, but had also noticed other examples like this - but it is a good reminder for me to double check with the developers that they consciously have done this and to register an interest that it stays that way (particularly as they strangely don’t provide

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

Sent from my iPhone > On 11 Jun 2018, at 08:02, Norbert Hartl wrote: > > > >> Am 11.06.2018 um 08:55 schrieb Richard O'Keefe : >> >> The order of key:value pairs in a JSON "object" >> is really NOT supposed to matter. For example, >> if you put {"a":1,"b":2} into a JSON database >> you

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

> Am 11.06.2018 um 08:55 schrieb Richard O'Keefe : > > The order of key:value pairs in a JSON "object" > is really NOT supposed to matter. For example, > if you put {"a":1,"b":2} into a JSON database > you should not be surprised to get {"b":2,"a":1} > back. Or vice versa, of course. > But

Re: [Pharo-users] Is it bad to have an order NeoJsonObject?

The order of key:value pairs in a JSON "object" is really NOT supposed to matter. For example, if you put {"a":1,"b":2} into a JSON database you should not be surprised to get {"b":2,"a":1} back. Or vice versa, of course. On 8 June 2018 at 00:16, Tim Mackinnon wrote: > Thanks guys - it seems