On 10/25/2013 04:22 PM, Tim Shen wrote:
On Fri, Oct 25, 2013 at 10:12 AM, Paolo Carlini
<paolo.carl...@oracle.com> wrote:
Ah good. Can't you just have split_bfs.cc defining the
_GLIBCXX_REGEX_DFS_QUANTIFIERS_LIMIT macro and including the existing
split.cc?
Here :) Hack the __FILE__ macro to let it report correctly.
Uhm, cute, didn't consider the naming issue, but I'm not sure we want to do that... What about having the code in a split.h and including it from split.cc and split_bfs.cc instead?

Paolo.

Reply via email to