Hi Hisham and Philipp
I am not sure the pull request is a safe implementation since
an error (not enough memory?) could occur after the malloc and before
the free... There is no way to let the compiler accept the problematic
construction? It would be not only safe but also a simpler code to read
and maintain :-)
I confess I forgot to do it my way and the problem is still open.
Sorry about that.
Tomás
On Fri, 10 Oct 2014, Hisham wrote:
On 10 October 2014 13:41, <alexandre.bertr...@tudor.lu> wrote:
Hi Philipp,
ok, thanks for the info. I opened an issue on GIT.
I'm not the maintainer of LuaSQL, but I have write access to the repo
and I noticed there's a pull request there which seems to be precisely
for the issue Philipp described:
https://github.com/keplerproject/luasql/pull/13/files
Is this it? I can merge it there.
-- Hisham
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
