> 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 be mapped anywhere, not just from a fixed 
starting offset. Otherwise they are the same as anything else.

> But again, this requires some sort of preprocessing in order to deal
> with the XSTRING(...), which are fixed at configure time. And if we
> accept to do the preprocessing, then I think we can statically build
> the array of the offsets.

Well, we can generate such files at compile time, similar to unicode data, 
default char tables, etc. Lots of tables are already generated. One more 
probably doesn't matter. The compiler can simply include this table. We could 
also include a default copy (another .dist file) in the source.

Regards,
Zoltan


-- 
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev 

Reply via email to