From: "v.shpilevoy@tarantool.org" <v.shpilevoy@tarantool.org>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: tarantool-patches@freelists.org
Subject: Re: [PATCH 2/5] lua: port console yaml formatting to C
Date: Wed, 21 Mar 2018 12:30:51 +0300 [thread overview]
Message-ID: <4C6FE419-35BE-4323-803A-624CAFC80522@tarantool.org> (raw)
In-Reply-To: <20180321091455.3td6h42oe3l2omlg@esperanza>
>>>
>>>> diff --git a/src/box/lua/console.lua b/src/box/lua/console.lua
>>>> @@ -395,4 +375,6 @@ package.loaded['console'] = {
>>>> on_start = on_start;
>>>> on_client_disconnect = on_client_disconnect;
>>>> completion_handler = internal.completion_handler;
>>>> + formatter = internal.formatter;
>>>
>>> I don't like that we export the serializer to Lua, but never use it in
>>> Lua code, only in C. Can't we create a serializer in C and pass it to
>>> the encoder function explicitly?
>>
>> The problem of Lua formatter is that it is Lua table, not cdata. And
>> to fully port it on C it is necessary to rewrite luaL_serializer and
>> l_dump in lyaml.cc <http://lyaml.cc/>, that seems to be too
>> complicated for a single propose - format push message. But if you
>> insist, I can do full port.
>
> I'm not sure... Obviously, I don't want you to rewrite the yaml encode.
> I just want to understand if there are alternatives to exporting the
> yaml encoder to the Lua console module, just to use it in C. Please take
> a look at how src/lua/msgpack.c is implemented - may be, we could borrow
> some ideas from it.
Ok, I will investigate.
next prev parent reply other threads:[~2018-03-21 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 13:34 [PATCH 0/5] session: introduce box.session.push Vladislav Shpilevoy
2018-03-19 13:34 ` [PATCH 1/5] session: forbid creation from Lua binary and applier sessions Vladislav Shpilevoy
2018-03-20 13:20 ` Vladimir Davydov
2018-03-20 13:46 ` v.shpilevoy
2018-03-19 13:34 ` [PATCH 2/5] lua: port console yaml formatting to C Vladislav Shpilevoy
2018-03-20 17:51 ` Vladimir Davydov
2018-03-20 18:04 ` v.shpilevoy
2018-03-21 9:14 ` Vladimir Davydov
2018-03-21 9:30 ` v.shpilevoy [this message]
2018-03-19 13:34 ` [PATCH 3/5] Remove empty function declaration Vladislav Shpilevoy
2018-03-20 17:55 ` Vladimir Davydov
2018-03-20 17:57 ` [tarantool-patches] " v.shpilevoy
2018-03-21 9:16 ` Vladimir Davydov
2018-03-19 13:34 ` [PATCH 4/5] session: introduce session_owner Vladislav Shpilevoy
2018-03-20 18:29 ` Vladimir Davydov
2018-03-19 13:34 ` [PATCH 5/5] session: introduce box.session.push Vladislav Shpilevoy
2018-03-21 9:10 ` Vladimir Davydov
2018-03-21 9:30 ` [tarantool-patches] " v.shpilevoy
2018-03-21 12:25 ` Vladimir Davydov
2018-03-19 13:41 ` [tarantool-patches] [PATCH 0/5] " v.shpilevoy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6FE419-35BE-4323-803A-624CAFC80522@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [PATCH 2/5] lua: port console yaml formatting to C' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox