From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id BAE4B316DA for ; Fri, 21 Jun 2019 18:34:36 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2wFulwFPtmX for ; Fri, 21 Jun 2019 18:34:36 -0400 (EDT) Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 730B3316CE for ; Fri, 21 Jun 2019 18:34:36 -0400 (EDT) Received: by mail-lj1-f179.google.com with SMTP id 16so7272227ljv.10 for ; Fri, 21 Jun 2019 15:34:36 -0700 (PDT) Date: Sat, 22 Jun 2019 01:34:33 +0300 From: Cyrill Gorcunov Subject: [tarantool-patches] Re: [RFC] box/lua/console: Add console.fmt module Message-ID: <20190621223433.GE24106@uranus> References: <20190620215405.9338-1-gorcunov@gmail.com> <20190621073241.GJ18958@atlas> <20190621081640.GB18551@uranus> <20190621121412.GB5998@atlas> <20190621200707.GD24106@uranus> <20190621203348.GC17212@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190621203348.GC17212@atlas> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Konstantin Osipov Cc: tarantool-patches@freelists.org, Alexander Turenko On Fri, Jun 21, 2019 at 11:33:48PM +0300, Konstantin Osipov wrote: > * Cyrill Gorcunov [19/06/21 23:11]: > > Thus if you're _quite_ sure that we better should use serpent then I'll > > try to prepare new version and we will see how it looks. > > No I am not but given no one made a detailed comparison I would > err on the side of an established module. To make a detailed compare I need more time, since you know I spent a lot of efforts simply to figure out how to merge new code into our builtin modules. > > Pretty printing multi-line output is a must btw. Ah, didnt know that. Will keep in mind, thanks!