unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Michael Olson <mwolson@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: json.el - JavaScript Object Notation parser / generator for Emacs Lisp
Date: Fri, 22 Feb 2008 09:30:10 +0900	[thread overview]
Message-ID: <87wsoxj0j1.fsf@catnip.gol.com> (raw)
In-Reply-To: <87myptub3c.fsf@grepfind.mwolson.org> (Michael Olson's message of "Thu, 21 Feb 2008 17:46:31 -0600")

Michael Olson <mwolson@gnu.org> writes:
>> Why did you put it in "net/"??  It's a formatted data I/O library, not
>> a network protocol...
>
> I placed it there because (1) I recall it being used by programs which
> interact with online services and (2) because it mentioned JavaScript,
> which is a language used in web-browsers.  Where else do you think it
> should go?

Dunno, but not net.  Probably just the root (lisp/).

Json is probably most directly comparable to xml.

-Miles

-- 
Fast, small, soon; pick any 2.




  parent reply	other threads:[~2008-02-22  0:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m21wwvfhbr.fsf@roisin.local>
     [not found] ` <E1FM3dc-0006c2-BV@fencepost.gnu.org>
     [not found]   ` <3b31caf90603220930k1f133151m81ab6986e9aff946@mail.gmail.com>
     [not found]     ` <E1FMVmY-0006om-Oi@fencepost.gnu.org>
2008-02-11 19:46       ` json.el - JavaScript Object Notation parser / generator for Emacs Lisp Edward O'Connor
2008-02-12 14:22         ` Leo
2008-02-12 20:59           ` Edward O'Connor
2008-02-12 18:39         ` Phil Hagelberg
2008-02-13  0:25         ` Richard Stallman
2008-02-14 14:15         ` T. V. Raman
2008-02-19 23:49         ` Edward O'Connor
2008-02-21 19:43           ` Michael Olson
2008-02-21 22:28             ` Miles Bader
2008-02-21 23:46               ` Michael Olson
2008-02-22  0:20                 ` Phil Hagelberg
2008-02-22  1:08                   ` Miles Bader
2008-02-22 22:56                   ` Richard Stallman
2008-02-22 23:11                     ` javascript.el (was: json.el - JavaScript Object Notation parser / generator for Emacs Lisp) Phil Hagelberg
2008-02-22 23:18                       ` javascript.el Lennart Borgman (gmail)
2008-02-23  0:35                         ` javascript.el Phil Hagelberg
2008-02-23  0:44                           ` javascript.el Lennart Borgman (gmail)
2008-02-23  0:28                       ` javascript.el (was: json.el - JavaScript Object Notation parser / generator for Emacs Lisp) Phil Hagelberg
2008-02-23 19:29                         ` Richard Stallman
2008-02-26 19:56                           ` Phil Hagelberg
2008-02-27 16:07                             ` Richard Stallman
2008-02-22  0:30                 ` Miles Bader [this message]
2008-02-22  1:25                   ` json.el - JavaScript Object Notation parser / generator for Emacs Lisp Michael Olson
2008-02-26  6:58                     ` Edward O'Connor

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/emacs/

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

  git send-email \
    --in-reply-to=87wsoxj0j1.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mwolson@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).