--- Comment #13 from Carlo Marcelo Arenas BelÃ³n <carenas@???> ---
(In reply to Zoltan Herczeg from comment #12) >
> I am not sure I follow. What is the right API? Passing an allocator?
IMHO the "right API" will have the following characteristics:
* It should be usable independently (ex: not relying in PCRE configure or other
options, even if it might be exported by it)
* It should be possible to use it at runtime (even if sljit is statically build
into the application (in this case the PCRE2 library, which is usually
dynamically linked into binaries)
* Will allow for a way to provide sljit with the memory it needs for both stack
(maybe even using MAP_STACK in Linux) and other pointers that might be needed
outside sljit (ex: friendly to DLOPEN or compiled malloc like libraries)
the easiest way might be to reuse PCRE's allocator API but then it wouldn't
satisfy the first requirement, and alternative would be to allow the memory
block to be provided by the library/application to sljit but that might
conflict with the third requirement.
You are receiving this mail because:
You are on the CC list for the bug.
This message was posted to the following mailing lists: