[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: large integer truncation in regex module
From: |
Paul Eggert |
Subject: |
Re: large integer truncation in regex module |
Date: |
Mon, 28 May 2012 22:27:18 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 |
On 05/28/2012 09:26 PM, Steven M. Schweda wrote:
> any environment-specific code really needs to be tested in
> the specific environment
Sure, that's important, but it's also important
to minimize the number of problems that can slip
through and be caught only by testing. Our tests
are not exhaustive, and can't be expected to be.
For properties where portable compile-time checks
are easy to do (as they are here), there's a good
argument for doing them.
> And it's impossible/impractical to arrange this
> commonality using #define (et al.)?
I'm sure one can do it with #if and #define as well,
but the result won't be appreciably simpler than the
"if (...)" version. And why bother? The "if (...)"
version has the advantage of more-portable
compile-time checking.