it's JavaScript nature where undefined is considered a "non-result" so you can consider it as a false, a null case, or a call that did not produce anything: undefined.
This concept is mainly present in the "each" method. If the callback deliberately returns false, the loop stops. jQuery does not want to force anybody to return something from a function that coul dbe used for whatever case returning different values. Scripting guys ;-) On Thu, Aug 6, 2009 at 9:44 AM, joop_eggen <joop.eg...@googlemail.com>wrote: > > In NetBeans IDE 7 there is a good JavaScript integration. For jQuery > there comes a long list of warnings. Especially one kind bothers me: > function does not always return a value. Is this an oversight due to > missing tools, or is this deliberate? > Though the nightly build is also concerned, I'll give some line > numbers of jquery-1.3.2.js: > 375, 1754, 1767, 1957, 2048, 2150, 2250, 2663, 2818, 2931, 3009. > I am quite willing to provide a corrected nightly build or whatever. > For us this issue could mean dropping jQuery altogether, and I am very > fond of jQuery. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
