On 10/04/2011 11:12 AM, Andre Poenitz wrote:
On Sun, Apr 10, 2011 at 10:31:47AM -0400, Richard Heck wrote:
On 04/09/2011 06:46 PM, Julien Rioux wrote:
I always saw those two warnings (paraphrased):
Lexer.cpp:197<anonymous> may be used uninitialized
void Lexer::Pimpl::verifyTable()
{
// [...]
if (table<- this line?
Doesn't look like this can ever be uninitialized. But if so,
valgrind should be able to come up with more details.
if (table
&& !lyx::sorted(table, table + no_items, CompareTags())) {
It seems to complain about CompareTags(). Perhaps it's just the
compiler's mistake. Running gcc 4.4.5 here.
Server.cpp:1018 ignoring return value of write(...)
This maybe the result of someone turning on -Wunused-result
or someone adding __attribute__ ((warn_unused_result)) to
the write() declaration.
Checking the return value might actually be a good idea to make
sure all the data was actually written.
Andre'
It's interesting that you can require the compiler to check for things
like this. Sounds like a good idea for critical code.
--
Julien
