tieske / pe-parser Goto Github PK

This is actually more of a question than an issue, but unfortunately I didn't any other avenue for asking it. I'm currently working on a project that will need to do some binary file parsing, and so I was looking at your project to get an idea of how people previously handled the task.

Anyways, I was wondering what your reasons were for implementing the toHex(IN, LEN) and toDec(IN) functions by hand, rather than using the built-in:

string.format("%0" .. tostring(LEN) .. "X", IN)

and

tonumber(IN, 16)

Your implementation of toHex seems to give the added benefit of being able to truncate the resulting string, but since I won't need that, I just wanted to make sure your decision wasn't based on there being a compatibility issue with string.format.

As seen here, pe-parser does not recognize the C runtime used by VS 2015.

Will try to provide binaries to test it or a patch myself.

-----Original Message-----
From: Philipp Janda [mailto:[email protected]]
Sent: maandag 13 april 2015 17:27
To: Hisham
Cc: Thijs Schreijer; Ignacio Burgueño
Subject: Re: prg-lr4win

<< SNIP >>

(Btw. @thijs, the pe-parser module doesn't recognize the debug versions
of the MSVC runtime DLLs, e.g. MSVCR100D.DLL.)