[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <A3E99621-443F-47DA-A728-7A97FC2B4DE5@gmail.com>
Date: Thu, 16 Jun 2016 17:30:26 +0200
From: Julien Ramseier <j.ramseier@...il.com>
To: musl@...ts.openwall.com
Subject: Re: tre regex in single regcomp.c file
> Le 16 juin 2016 à 17:25, Rich Felker <dalias@...c.org> a écrit :
>>
>> creating internal interfaces for implementing a single
>> self-contained public function (regcomp) is bad design.
>>
>> (even if you split the code up, all the code will be
>> linked together if the public api symbol is referenced
>> otherwise none of the code will be used, so you just
>> create linking overhead and headaches around the internal
>> api between the source files which must obey posix
>> namespace rules etc.)
>
> Yes, the main motivation was to get rid of external namespace
> pollution without renaming all the internal functions to be
> __-prefixed, and also to allow inter-procedural analysis
> optimizations.
>
That makes sense.
Thank you both for the explanations.
- Julien
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
