From: EBo <eb...@us...> - 2014-04-20 06:28:14
|
This was bothering me enough that I just went in and patched the source files. It was a little more involved than I thought, but not that much. Attached are two patches to correct the problem. Can someone(s) else do some testing with them and give me feedback? Thanks and best regards, EBo -- On Apr 7 2014 3:22 AM, andy pugh wrote: > On 7 April 2014 08:23, EBo <eb...@us...> wrote: >> I guess the question is that if we can fix it, should we? What is >> the >> prognosis of a replacement? I know people have been talking about >> it >> for a decade or more now, so if there is not one on the horizon, >> then >> maybe we should look at least taking care of the low hanging >> fruit... > > I think every instance in that list was in libnml. > It is unlikely that when writing NML anyone wrote "u_long" to mean > anything other than "unsigned 32". And especially unlikely that they > meant "I don't care if this is 32 bits or 64 bits" > So, a global search and replace might be an acceptable move. But not > one I feel like performing. > > -- > atp > If you can't fix it, you don't own it. > http://www.ifixit.com/Manifesto > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers |