From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: Sergey Bronnikov <estetus@gmail.com>, tarantool-patches@dev.tarantool.org, max.kokryashkin@gmail.com Subject: Re: [Tarantool-patches] [PATCH luajit 1/2][v2] Fix embedded bytecode loader. Date: Tue, 12 Sep 2023 13:20:08 +0300 [thread overview] Message-ID: <685a57df-a7e7-a1ab-aac0-6b4b64e24c8d@tarantool.org> (raw) In-Reply-To: <ZP7Tuq_eo-Ek_yBl@root> Hi, On 9/11/23 11:45, Sergey Kaplun wrote: > Hi, Sergey! > Thanks for the fixes! > > On 07.09.23, Sergey Bronnikov wrote: >> Hi, Sergey >> <snipped> >> >>> | "" >>> >>> Nit: use single quotes instead of double quotes if possible. >> Without context it is difficult to get what is line you talk about. >> >> As I see everything is fine with quotes in version on the branch. >> > I'm talking about the same line (got this version from the branch): > > | +local function basename(path) > | + return path:match("[^/]*$") > | +end Fixed. --- a/test/tarantool-tests/utils/tools.lua +++ b/test/tarantool-tests/utils/tools.lua @@ -10,7 +10,7 @@ function M.basedir(path) end function M.basename(path) - return path:match("[^/]*$") + return path:match('[^/]*$') end function M.profilename(name) >>> Nit: `[^/\\]` is better since it also covers Windows. >>> See <test/lua-Harness-tests/314-regex.t:167> >>> | local dirname = arg[0]:gsub('([^/\\]+)$', '') >>> Since we don't support Windows feel free to ignore. >>> >>>> +end >>>> + >>>> +local stdout_msg = 'Lango team' >>>> +local lua_code = ('print(%q)'):format(stdout_msg) >>>> +local fpath = os.tmpname() >>>> +local path_lua = ('%s.lua'):format(fpath) >>>> +local path_c = ('%s.c'):format(fpath) >>>> +local path_so = ('%s.so'):format(fpath) >>> Minor: I suppose it should be renamed to `path_shared`, since on macOS >>> they have the ".dyld" suffix for shared libs. Hence, we need to use the >>> suffix in format of the shared library name too. You may take some >>> inspiration from here [1]. >> Fixed. > Hmm, I don't see these updates on the branch [1]. Maybe you forgot to push > your local changes to the repository (*)? Right, I forgot to force-push ;( Force-pushed now. <snipped> >>> Nit: Indent is 4 spaces instead of 2. >>> >>>> + return path:match('(.*' .. sep .. ')') or './' >>> It's better to mention that the pattern matching is greedy, so we match >>> until the last separator. >> >> Updated. > This is missing too (*). Added a comment. > <snipped>
next prev parent reply other threads:[~2023-09-12 10:20 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-31 11:29 [Tarantool-patches] [PATCH luajit 0/2][v2] " Sergey Bronnikov via Tarantool-patches 2023-08-31 11:30 ` [Tarantool-patches] [PATCH luajit 1/2][v2] " Sergey Bronnikov via Tarantool-patches 2023-08-31 11:49 ` Sergey Bronnikov via Tarantool-patches 2023-09-01 9:42 ` Maxim Kokryashkin via Tarantool-patches 2023-09-04 9:31 ` Sergey Bronnikov via Tarantool-patches 2023-09-05 6:34 ` Maxim Kokryashkin via Tarantool-patches 2023-09-05 14:10 ` Sergey Kaplun via Tarantool-patches 2023-09-07 15:21 ` Sergey Bronnikov via Tarantool-patches 2023-09-11 8:45 ` Sergey Kaplun via Tarantool-patches 2023-09-12 10:20 ` Sergey Bronnikov via Tarantool-patches [this message] 2023-10-31 11:30 ` Sergey Kaplun via Tarantool-patches 2023-09-05 14:12 ` Sergey Kaplun via Tarantool-patches 2023-09-07 7:06 ` Sergey Bronnikov via Tarantool-patches 2023-08-31 11:32 ` [Tarantool-patches] [PATCH luajit 2/2][v2] Followup fix for " Sergey Bronnikov via Tarantool-patches 2023-09-01 10:05 ` Maxim Kokryashkin via Tarantool-patches 2023-09-04 16:34 ` Sergey Bronnikov via Tarantool-patches 2023-09-05 6:45 ` Maxim Kokryashkin via Tarantool-patches 2023-09-05 12:55 ` Sergey Kaplun via Tarantool-patches 2023-09-07 7:04 ` Sergey Bronnikov via Tarantool-patches 2023-09-11 9:26 ` Sergey Kaplun via Tarantool-patches 2023-09-12 10:30 ` Sergey Bronnikov via Tarantool-patches
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=685a57df-a7e7-a1ab-aac0-6b4b64e24c8d@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=max.kokryashkin@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 1/2][v2] Fix embedded bytecode loader.' \ /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