Philip, Zoltán,
Thanks for you feedback. Comments inline below.
I wouldn't worry about the thread safety of your static array. If you
write the same values to the memory from different threads, that is
safe. Therefore, if for some reasons the array would be initialized
multiple times, that
On Mon, 31 Dec 2012, Kevin Connor Arpe wrote:
Apologies, I should be clearer. By first I do not mean multiple errors
in the same pattern. I mean multiple, sequential calls to pcre_compile().
Imagine the scenario above where user is entering regex in a GUI. This
causes continuous recompile
On 1 January 2013 14:12, Philip Hazel p...@hermes.cam.ac.uk wrote:
On Mon, 31 Dec 2012, Kevin Connor Arpe wrote:
Apologies, I should be clearer. By first I do not mean multiple errors
in the same pattern. I mean multiple, sequential calls to pcre_compile().
Imagine the scenario above where
Each user gets its own writable data section; read-only data sections
are instead shared between the users.
I don''t think anything would work without a private .data and .bss section. As
far as I remember the point of static libraries is that they use position
independent code, so they can
--- You are receiving this mail because: ---
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1326
--- Comment #2 from Zoltan Herczeg hzmes...@freemail.hu 2013-01-01 21:43:43
---
I think the code is safe, and hopefully works on Intel C and SUNPRO C
compilers,
