From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Nikita Pettik <korablev@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 2/4] sql: refactor sqlVdbeMemNumerify() Date: Tue, 11 Feb 2020 23:17:21 +0100 [thread overview] Message-ID: <04b6832e-212e-a323-63bf-962b35196f12@tarantool.org> (raw) In-Reply-To: <20200211141427.GC5168@tarantool.org> Hi! Thanks for the fixes! I've pushed my review fixes on top of this commit. See it in the end of the email, and on the branch. I aligned the comment by 66 symbols, and changed '@mem' to '@a mem' in a second place. Talking of your questions - why do we use @a? I think just because it was needed to choose something and @a was chosen. From what I remember, doxygen does not have a special command for mentioning function parameters inside function's description. So there was no a standard way. ================================================================================ commit bde8e58b05c5e4d3c650eea10e5905ce228b943d Author: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Date: Tue Feb 11 23:07:36 2020 +0100 Review fixes diff --git a/src/box/sql/vdbeInt.h b/src/box/sql/vdbeInt.h index 9ecf7a486..38305ce1d 100644 --- a/src/box/sql/vdbeInt.h +++ b/src/box/sql/vdbeInt.h @@ -535,11 +535,12 @@ int mem_apply_integer_type(Mem *); int sqlVdbeMemRealify(Mem *); /** - * Convert @a mem to NUMBER type, so that after conversion it has one - * of types MEM_Real, MEM_Int or MEM_UInt. If conversion is not possible, - * function returns -1. + * Convert @a mem to NUMBER type, so that after conversion it has + * one of types MEM_Real, MEM_Int or MEM_UInt. If conversion is + * not possible, function returns -1. * - * Beware - this function changes value and type of @mem argument + * Beware - this function changes value and type of @a mem + * argument. */ int vdbe_mem_numerify(struct Mem *mem);
next prev parent reply other threads:[~2020-02-11 22:17 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-05 16:19 [Tarantool-patches] [PATCH 0/4] sql: fix NUMBER conversion issues Nikita Pettik 2020-02-05 16:19 ` [Tarantool-patches] [PATCH 1/4] sql: remove cast to INT during FP arithmetic ops Nikita Pettik 2020-02-05 16:19 ` [Tarantool-patches] [PATCH 2/4] sql: refactor sqlVdbeMemNumerify() Nikita Pettik 2020-02-10 23:25 ` Vladislav Shpilevoy 2020-02-11 14:14 ` Nikita Pettik 2020-02-11 22:17 ` Vladislav Shpilevoy [this message] 2020-02-05 16:19 ` [Tarantool-patches] [PATCH 3/4] sql: fix CAST AS NUMBER operator Nikita Pettik 2020-02-10 23:24 ` Vladislav Shpilevoy 2020-02-11 14:14 ` Nikita Pettik 2020-02-11 22:17 ` Vladislav Shpilevoy 2020-02-11 23:20 ` Nikita Pettik 2020-02-11 23:27 ` Vladislav Shpilevoy 2020-02-12 14:10 ` Nikita Pettik 2020-02-05 16:19 ` [Tarantool-patches] [PATCH 4/4] sql: do not force FP representation for NUMBER field Nikita Pettik 2020-02-10 23:24 ` Vladislav Shpilevoy 2020-02-11 14:14 ` Nikita Pettik 2020-02-09 17:39 ` [Tarantool-patches] [PATCH 0/4] sql: fix NUMBER conversion issues Vladislav 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=04b6832e-212e-a323-63bf-962b35196f12@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=korablev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/4] sql: refactor sqlVdbeMemNumerify()' \ /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