On 24/05/22 18:54, Maynard, Christopher via Wireshark-dev wrote:
-----Original Message-----
From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf
Of João Valverde
Sent: Monday, May 23, 2022 2:37 PM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] Move to Lua 5.3/5.4?
I'm not sure how far that simple strategy will go (not very?). Maybe
someone else with more experience using multiple Lua versions can
answer that.
I vaguely recall trying something like that for a different purpose, but without success. Regardless, even if scripts can't be modified to work with different versions of Lua, I'm still very much in favor of moving to at least 5.3 for the Wireshark 4.0 release, just as I was 5 years ago prior to Wireshark 3.0 being released, backward compatibility be damned. With 3.6 currently scheduled for long-term support until May 22, 2024 (https://gitlab.com/wireshark/wireshark/-/wikis/Development/LifeCycle), people will have plenty of time to migrate their scripts. For me personally, I can't wait to migrate mine to use native Lua bit operators.
https://gitlab.com/wireshark/wireshark/-/merge_requests/7024
Test suite passes using Lua 5.3. If you could test this change that
would be great. I don't use the Wireshark Lua API.
Note there's no Windows build yet. The Lua package needs to be updated.
That is a whole other thing.