On 20 Sep 2010, at 17:58, Aparajita Fishman wrote:
If you got 4 consecutive runtime errors immediately after calling A4D GET SESSION STATS, I wouldn't consider that working fine!
I don't actually get 4 consecutive runtime errors until it's been working fine for for about 5 hours, during which 200,000 dynamic requests have been served. The session stats are returned correctly during this time.
Also, I'm still not sure that it's this piece of code that's causing the problem - all I've got to go on is that it has 4 x 'CLEAR_ARRAYs' and I get 4 runtime errors (so - likely), but CLEAR_ARRAY is all over the application.
I'm at the point with 4D where I've lost confidence in anything but my own eyes to determine how a function works. As a 'random' example (one of several), the docs say that DELETE FOLDER should return a -47 error if it's got something in it. But in fact it doesn't even call the error handler for this condition. So file another bug report and ditch the bit of logic that depended on that behavior. They also say that 'Method called on error' should return the current error handler, but it doesn't. That's been the story of my life for the last few months.
I know I'm talking about 4D here and you're making a point re. plugins and components, however, working in a 'buggy' environment can instill a kind of mistrust of anything other than observed behavior which is not a very healthy approach.
I don't know what it must be like doing plugins - you must have climbed a few walls by now :-)
Regards Peter _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
