unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-json 0.2.0 released
Date: Fri, 5 Apr 2013 09:35:03 +0200	[thread overview]
Message-ID: <CAMFYt2bDcc4zdDqBfH=MM-1fFJkWvBYMnu8d62dOmoO2CdcGvQ@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoUa+RhzQSBz5wQfdF8nmzcAWOyxQ=UQ4xh30hFd4shMVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

2013/4/5 Aleix Conchillo Flaqué <aconchillo@gmail.com>

> Thank you both for the comments.
>
> I must admit that I got kind of lost and I ended up not knowing if you
> had any specific suggestions for guile-json. It is my very first guile
> (scheme) package and I am pretty new to scheme.
>
> From what I understood, the main concerns were:
>
> 1. Hash tables might not be a proper way to represent JSON objects.
>
> 2. Syntax for accessing JSON objects.
>
> For 1, as Taylan mentioned, json.org clearly says that JSON objects
> are unordered. So I thought a hash table was the right data structure
> to use. I initially thought about using association lists, but that's
> ordered and performance might be worst for large objects.
>

Yes, so as it turns out, it was my ignorance that caused me to raise this
topic :)
Hash tables are fine, but I think that guile's support for them isn't
convinient, because their print representation isn't very informative
(which occured to me when I was trying to test how exactly guile-json works)


> May be it would be better to have a json-object type and procedures to
> access it (json-object-ref ...) and internally it could be a hash
> table, or an alist. Then, maybe, the user could specify if he wants to
> get ordered json-objects or not, and internally use hash tables or
> alists.
>

I think that, if the specification says that it's unordered, there's no
actual need to complicate things overly :)


> For 2, yes, a better syntax would be ideal. I don't know about
> SRFI-105, but I'll take a look into it.
>
> SRFI-105 offers only infix/m-exp notation within curly braces and a more
decent way to index arrays (using postfix brackets, as in most popular
programming languages)

Sorry if I caused unnecessary confusion ;o

Best regards
M.

[-- Attachment #2: Type: text/html, Size: 2761 bytes --]

  reply	other threads:[~2013-04-05  7:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  7:08 guile-json 0.2.0 released Aleix Conchillo Flaqué
2013-04-04  9:11 ` Panicz Maciej Godek
2013-04-04 10:15   ` Taylan Ulrich B.
2013-04-04 12:06     ` Panicz Maciej Godek
2013-04-04 22:21       ` Taylan Ulrich B.
2013-04-04 22:59         ` Aleix Conchillo Flaqué
2013-04-05  7:35           ` Panicz Maciej Godek [this message]
2013-04-04 23:39         ` Daniel Hartwig
2013-04-07 11:40         ` Panicz Maciej Godek
2013-04-07 20:38           ` Taylan Ulrich B.
2013-04-08  1:51             ` Daniel Hartwig
2013-04-08  2:11           ` Daniel Hartwig
2013-04-05  0:17       ` Daniel Hartwig
2013-04-05  2:47         ` Noah Lavine
2013-04-05  9:35           ` Daniel Hartwig
2013-04-05 13:18             ` Noah Lavine
2013-04-05  9:41         ` Panicz Maciej Godek
     [not found]     ` <CAPjoZodAaHLfPGb+XiUhoMJD7J4_kYrjRmYP+p1S5w5yuPgLEg@mail.gmail.com>
     [not found]       ` <CAPjoZoc12W4usGnkwSZG2zNqe8xF6C4hWWZgq+-Nc8HMg_Xw4Q@mail.gmail.com>
2013-04-04 15:11         ` Nala Ginrut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMFYt2bDcc4zdDqBfH=MM-1fFJkWvBYMnu8d62dOmoO2CdcGvQ@mail.gmail.com' \
    --to=godek.maciek@gmail.com \
    --cc=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).