This is a long standing gripe by some. Many functions return empty if no error was encountered. As previously mentioned, if you were able to contact a URL and it returned data, then from the engine's perspective, there was no error.
Some have suggested a feature/fix to the result that it would always return something, instead of just empty, but that would require a great deal of refactoring by everyone who's code checks the result in any way. That kind of change is like pulling the last tooth from a ravenous lion. Who will perform the surgery, and then suffer the ire of the general LC community? There would have to be some other variable that was returned instead, like the realresult or the extendedresult (extresult) or the result ["successmsg"]. Bob S > On Feb 25, 2018, at 07:26 , jbv via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Mike > Thanks for your reply. > Actually, in the 2 cases I mentioned, I was able to find the origin of the > problem. > The only point I was trying to make is that each time the result was of no > help since it remained empty. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
