On Sat, 2008-08-30 at 20:12 +0100, Neil Williams wrote: > > And it's not > > just one option which noneone uses. it's quite likely that many users > > will try to run program that way and then it crashes. > > Actually, a lot of programs need to be tested in different ways, > providing options and passing files on the command line.
You can do that directly from Anjuta too. > I use Anjuta for six or seven upstream C projects - not once have I > needed to execute the program from the Build menu - it is almost never > appropriate. If you want to lower the severity then do so. But if the only reason is that YOU don't need that feature then I really don't understand. You really should not try to decide what feature users need or want to use, just make the damn thing work. > > > The compiled program can be executed normally outside Anjuta. > > > > > > The compiled program can be executed normally *within the terminal* in > > > Anjuta. > > > > Yes you can do that, but I think that's just a poor excuse. > > Not at all - it is vital to be able to pass arbitrary options that > change with each test. As I already said you can pass options to program directly from Anjuta too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
