On do, 2012-04-12 at 01:54 +0200, Benoît Minisini wrote: > The bug was in Gambas 3.0. Now, in Gambas 3.1, if you try to run a > program that does not exist, you get an error.
If the bug is in Gambas 3.0 it is also in Gambas 2 because I used the exact same code for both Gambas 2 and 3.0 (without the TRY and checking for length of returned string -> as no errors are generated) Now I'm stuck with two different approaches as TRY in Gambas 2.x and 3.0 will NOT generate an error and thus returns me the wrong information. So the 2.x and 3.0 code will not work for 3.1 The 3.1 code will not work for 2.x and 3.0 I loved the fact that both versions used exactly the same code. Makes maintaining them a lot easier. But that is in the past now :-( I actually preferred the fact that, even if a command was not present, no error was generated when running it. It simply returned me an empty string when using EXEC, which is great for testing if a command is present or not using the LEN() function. For now my whole project is on a complete hold because of this, as TRY seems to open processes in 3.1 that do not get closed when closing the application (see other posts) :-( ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Gambas-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gambas-user
