Re: [Libmesh-devel] Policy on contrib warnings

[Derek G. <fri...@gm...>]

On Fri, Jul 11, 2008 at 9:49 AM, John Peterson <jwp...@gm...> wrote:

> Try to use your best programming judgment as well.  If something
> actually seems dangerous/might cause a problem in some use cases, I
> would definitely fix it.  Sometimes warnings are good for stuff like
> that :)
>

Wow - how right you were!

After looking into it a bit more... all of the warnings were when calling
one particular function (ex_id_lkup) from Exodus.  I went to look at the
definition of that function... and noticed that it just didn't jive with
what Nemesis was trying to pass into it... I mean... the actual body of the
function didn't look like it would work with what Nemesis was passing in.

Then I went back to sourceforge and looked at that same function from
Exodus.... and lo and behold... there's been MASSIVE changes to Exodus on
sourceforge!  There apparently was a big sync between the repos at Sandia
and the sourceforge.net repo about 4 months ago.  That means that our copy
of Exodus is out of sync with the copy of Nemesis I grabbed today.

So... I'm going to try to update our copy of Exodus from sourceforge...
hopefully it doesn't break anything... sigh.  Either way, it has to be done.

Derek