From: Raymond I. <xw...@ya...> - 2003-07-27 03:05:24
|
Do we really have to support the buggy NN4.03? Should we really be adding "return null;" to all our functions? I think we should support the ns4 that's less buggy such as 4.7 (at least) PS. We just can't win them all :( -- Raymond Irving --- C Kissinger <cki...@ne...> wrote: > I think this API is great, and I got v3, but even > though the > > docs say it's supported for NN4+, (yes I know it's a > beta) > > it seems it has been tested on NN 4.73: the most > "stable" NN4. > > > > I have found that 4.03 is even flakier, which is why > I use it. > > Every example had a bucketful of errors, most of > them > > stemming from a "function does not always return a > value" error. > > > > There are a lot of empty "return;" statements in the > code, so > > I made a quick hack by replacing them with "return > null;". That > > took care of many of the errors, not all. The rest > (still stemming > > from the "function does not always return a value" > errors) were > > from conditional return statements in a function, > without a final > > "default" return statement if none of the conditions > are met. So > > I added "return null;" to these functions as well. > > > > I don't know if I broke anything by doing this, but > going one by > > one through the examples and adding "return null;" > statements > > as I found errors, I got up to the "MotionX" example > and > > everything that far works fine now on NN 4.03, NS > 7.02, IE 6, > > and Mozilla 1.4 in WinXP. > > > > I intend to test on Linux later. > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |