From: "n.pettik" <korablev@tarantool.org> To: tarantool-patches@freelists.org Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Subject: [tarantool-patches] Re: [PATCH v2 2/4] sql: refactor getNewIid() function Date: Fri, 29 Mar 2019 21:15:54 +0300 [thread overview] Message-ID: <611549C1-8E50-42E2-9242-1E5CE9AE4D74@tarantool.org> (raw) In-Reply-To: <32bf26dc-79ef-6bee-725a-2e1acf37d297@tarantool.org> [-- Attachment #1: Type: text/plain, Size: 1609 bytes --] >> diff --git a/src/box/sql/build.c b/src/box/sql/build.c >> index 8fb001433..f55f6d800 100644 >> --- a/src/box/sql/build.c >> +++ b/src/box/sql/build.c >> @@ -1918,45 +1918,43 @@ sql_drop_foreign_key(struct Parse *parse_context) >> sqlVdbeChangeP5(sqlGetVdbe(parse_context), OPFLAG_NCHANGE); >> } >> >> -/* >> - * Generate code to determine next free Iid in the space identified by >> - * the iSpaceId. Return register number holding the result. >> +/** >> + * Generate code to determine next free index id in >> + * the space identified by the @space_id. > > 1. According to doxygen docs http://www.doxygen.nl/manual/commands.html <http://www.doxygen.nl/manual/commands.html> > there is no such a command as @space_id. But obviously I know what > you've implied here. For references to parameters we use '@a' before a > parameter. Like this: > ... > * the space identifier by @a space_id. > ... Does anybody even try to generate doxygen doc? I still believe that doxygen format may be useful only for external (aka interface) functions. The rest of comments (especially for static funcs) are seem to be aimed solely at developers. > Note that I deliberately used @return instead of @retval, because > @return has no arguments - it is just a description. > > ================================================================= > > commit 9e77985d09e53332d87b323c6ef74b747c418d8e > Author: Vladislav Shpilevoy <v.shpilevoy@tarantool.org <mailto:v.shpilevoy@tarantool.org>> > Date: Thu Mar 28 15:53:24 2019 +0300 > > Review fix Thx, applied. [-- Attachment #2: Type: text/html, Size: 15241 bytes --]
next prev parent reply other threads:[~2019-03-29 18:15 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-28 12:07 [tarantool-patches] [PATCH v2 0/4] Introduce ALTER TABLE ADD CONSTRAINT PK/UNIQUE Nikita Pettik 2019-03-28 12:07 ` [tarantool-patches] [PATCH v2 1/4] sql: rework ALTER TABLE grammar Nikita Pettik 2019-03-28 12:07 ` [tarantool-patches] [PATCH v2 2/4] sql: refactor getNewIid() function Nikita Pettik 2019-03-28 15:11 ` [tarantool-patches] " Vladislav Shpilevoy 2019-03-29 18:15 ` n.pettik [this message] 2019-04-01 5:17 ` Konstantin Osipov 2019-03-28 12:07 ` [tarantool-patches] [PATCH v2 3/4] sql: fix error message for improperly created index Nikita Pettik 2019-03-28 14:01 ` [tarantool-patches] " Konstantin Osipov 2019-03-28 15:11 ` Vladislav Shpilevoy 2019-03-29 18:16 ` n.pettik 2019-03-28 12:07 ` [tarantool-patches] [PATCH v2 4/4] sql: introduce ALTER TABLE ADD CONSTRAINT UNIQUE/PRIMARY KEY Nikita Pettik 2019-03-28 15:11 ` [tarantool-patches] " Vladislav Shpilevoy 2019-03-29 18:16 ` n.pettik 2019-04-01 17:58 ` Vladislav Shpilevoy 2019-04-03 7:57 ` [tarantool-patches] Re: [PATCH v2 0/4] Introduce ALTER TABLE ADD CONSTRAINT PK/UNIQUE Kirill Yukhin
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=611549C1-8E50-42E2-9242-1E5CE9AE4D74@tarantool.org \ --to=korablev@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=v.shpilevoy@tarantool.org \ --subject='[tarantool-patches] Re: [PATCH v2 2/4] sql: refactor getNewIid() function' \ /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