Re: Channel commands: special characters, quotes and escaping

On Thursday, May 26, 2016 at 12:43:21 AM UTC+2, ZyX wrote:
> Most of time JSON is not written "by hand", it is created by some
> library functions. E.g. Python has `json` standard (almost always
> installed with the interpreter itself) module, VimL has built-in
> `json_encode`, etc: many modern languages have this either "built-in"
> or "in standard library", exceptions are usually positioning
> themselves as "system" (like Rust or C) or "light-weight" (like lua)
> languages. These functions would not create invalid JSON, they accept
> native data types and they may be optimized, so 99% of time it is
> better to use them even if you are absolutely sure you can write valid
> JSON by hand.
Thanks for that. For writing services/plugins/whatever I would, of course, rely on those libraries. I simply didn't have the need to do so in the past. That's why my knowledge about JSON is rather limited.

Right now, I have a particular use case - I'm playing with the new functions for a review of the upcoming version. So, I was looking for a simple example to be put in the article. Basically, I'm satisfied with telling the readers the default handler expects JSON.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.