On 2012-11-26 20:32:17 +0100, olivier sallou wrote:
XML is nice for internal config, message/config exchanges, etc... help with
its structure and its DTD to force/help understanding the schema.
BUT definitely not useable by an end user for end-user config. It is very
hard to read (opening an
On 11/27/2012 05:40 PM, Vincent Lefevre wrote:
On 2012-11-26 20:32:17 +0100, olivier sallou wrote:
XML is nice for internal config, message/config exchanges, etc... help with
its structure and its DTD to force/help understanding the schema.
BUT definitely not useable by an end user for
* Ivan Shmakov oneing...@gmail.com, 2012-11-26, 14:32:
Seriously, XML takes a lot of concerns off an application programmer.
It provides quoting, arbitrary hierarchical structure, support for
different encodings, etc. Why, don't you think that $ grep
'[[:lower:]]' FILE is ever supposed to
On 26/11/2012 19:52, Jakub Wilk wrote:
* Ivan Shmakov oneing...@gmail.com, 2012-11-26, 14:32:
Seriously, XML takes a lot of concerns off an application programmer. It
provides quoting, arbitrary hierarchical structure, support for different
encodings, etc. Why, don't you think that $ grep
Jakub Wilk jw...@debian.org writes:
* Ivan Shmakov oneing...@gmail.com, 2012-11-26, 14:32:
Seriously, XML takes a lot of concerns off an application
programmer. It provides quoting, arbitrary hierarchical structure,
support for different encodings, etc. Why, don't you think that
$ grep
Norbert Preining prein...@logic.at writes:
[...]
Ever heard of grep, sed, awk, all these nice things that make
your life happy. Trash them when you are doing XML.
JFTR: there's xmlstarlet(1), which is capable enough to replace
awk(1), sed(1), and grep(1) (which is
6 matches
Mail list logo
