Thread overview | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
October 19, 2003 DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Just a few more requests with Charles' DIDE. With the compiler output (and this may be something Walter can address), I would be nice to know if it was a success or failure (VC does this), parhaps with some stats like the size of the file created. ie Success - test.exe (75kb) //or Failure - test.exe 10 errors. As (at least for me), that's much faster to interpret, before looking for error messages. With compile and run, it still runs the old-program when it fails to compile. I'd be nice if at least DIDE brought up a warning message, although I'd expect it not to run at all. Another thing in DIDE, is that if the compiler fails and no exe exists it brings up the folder where the exe should be. Is this suppose to occur? I like the automatic d file association because I can be reading the D newsgroup and load up anybodies d code in the DIDE browser in a few clicks, however I can't compile an run them. In other words, it would be nice to be able to compile and run non-project files. -Anderson |
October 19, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to J Anderson | > Success - test.exe (75kb) Good idea Ill add it. > it would be > nice to be able to compile and run non-project files. You should be able to compile it, the new version will have Dos Prompt and Explorer commands in the Tools menu that will jump to the project dir to execute it. Lots of changes for new version Ill upload tonight. I wanted to bundle it with YT's win32 lib, and create some wrappers for the functinos but theres never enough time. C "J Anderson" <anderson@badmama.com.au.REMOVE> wrote in message news:bmud1u$1ueq$1@digitaldaemon.com... > Just a few more requests with Charles' DIDE. > > With the compiler output (and this may be something Walter can address), I would be nice to know if it was a success or failure (VC does this), parhaps with some stats like the size of the file created. ie > > Success - test.exe (75kb) > //or > Failure - test.exe 10 errors. > > As (at least for me), that's much faster to interpret, before looking > for error messages. > > With compile and run, it still runs the old-program when it fails to compile. I'd be nice if at least DIDE brought up a warning message, although I'd expect it not to run at all. > > Another thing in DIDE, is that if the compiler fails and no exe exists > it brings up the folder where the exe should be. Is this suppose to occur? > > I like the automatic d file association because I can be reading the D newsgroup and load up anybodies d code in the DIDE browser in a few clicks, however I can't compile an run them. In other words, it would be nice to be able to compile and run non-project files. > > -Anderson > |
October 19, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Charles Sanders | Charles Sanders wrote:
>
>Lots of changes for new version Ill upload tonight. I wanted to bundle it
>with YT's win32 lib, and create some wrappers for the functinos but theres
>never enough time.
>
>C
>
>
>
I can't wait :)
|
October 20, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to J Anderson | > Success - test.exe (75kb) > //or > Failure - test.exe 10 errors. Actually the only way to test this is to record the executable size ( which may change so this wont work either ) , and compare them, because even in an unsuccessful build an .exe is created of some size. Anyone have any ideas on how to test if a build succeeds ? Other than manually parsing the results ? C "J Anderson" <anderson@badmama.com.au.REMOVE> wrote in message news:bmud1u$1ueq$1@digitaldaemon.com... > Just a few more requests with Charles' DIDE. > > With the compiler output (and this may be something Walter can address), I would be nice to know if it was a success or failure (VC does this), parhaps with some stats like the size of the file created. ie > > Success - test.exe (75kb) > //or > Failure - test.exe 10 errors. > > As (at least for me), that's much faster to interpret, before looking > for error messages. > > With compile and run, it still runs the old-program when it fails to compile. I'd be nice if at least DIDE brought up a warning message, although I'd expect it not to run at all. > > Another thing in DIDE, is that if the compiler fails and no exe exists > it brings up the folder where the exe should be. Is this suppose to occur? > > I like the automatic d file association because I can be reading the D newsgroup and load up anybodies d code in the DIDE browser in a few clicks, however I can't compile an run them. In other words, it would be nice to be able to compile and run non-project files. > > -Anderson > |
October 20, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Charles Sanders | Charles Sanders wrote:
>>Success - test.exe (75kb)
>>//or
>>Failure - test.exe 10 errors.
>
>
> Actually the only way to test this is to record the executable size ( which
> may change so this wont work either ) , and compare them, because even in an
> unsuccessful build an .exe is created of some size.
>
> Anyone have any ideas on how to test if a build succeeds ? Other than
> manually parsing the results ?
>
> C
What about the return code? Every console application returns an integer to the shell. (this is how utilities like make know when to stop)
-- andy
|
October 20, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Andy Friesen | Good thinking ill test it out. Also does anyone know where I can get that socket.d inherited from Stream ? Charles "Andy Friesen" <andy@ikagames.com> wrote in message news:bn1p38$1rih$1@digitaldaemon.com... > Charles Sanders wrote: > >>Success - test.exe (75kb) > >>//or > >>Failure - test.exe 10 errors. > > > > > > Actually the only way to test this is to record the executable size ( which > > may change so this wont work either ) , and compare them, because even in an > > unsuccessful build an .exe is created of some size. > > > > Anyone have any ideas on how to test if a build succeeds ? Other than manually parsing the results ? > > > > C > > What about the return code? Every console application returns an integer to the shell. (this is how utilities like make know when to stop) > > -- andy > |
October 20, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Charles Sanders | NM i found it , changed news readers finnaly. Im using Free Agent what is everyone else using ? C "Charles Sanders" <sanders-consulting@comcast.net> wrote in message news:bn1pmc$1sil$1@digitaldaemon.com... > Good thinking ill test it out. > > Also does anyone know where I can get that socket.d inherited from Stream ? > > > Charles > "Andy Friesen" <andy@ikagames.com> wrote in message > news:bn1p38$1rih$1@digitaldaemon.com... > > Charles Sanders wrote: > > >>Success - test.exe (75kb) > > >>//or > > >>Failure - test.exe 10 errors. > > > > > > > > > Actually the only way to test this is to record the executable size ( > which > > > may change so this wont work either ) , and compare them, because even > in an > > > unsuccessful build an .exe is created of some size. > > > > > > Anyone have any ideas on how to test if a build succeeds ? Other than manually parsing the results ? > > > > > > C > > > > What about the return code? Every console application returns an integer to the shell. (this is how utilities like make know when to stop) > > > > -- andy > > > > |
October 21, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Andy Friesen | Your so smart ;). C "Andy Friesen" <andy@ikagames.com> wrote in message news:bn1p38$1rih$1@digitaldaemon.com... > Charles Sanders wrote: > >>Success - test.exe (75kb) > >>//or > >>Failure - test.exe 10 errors. > > > > > > Actually the only way to test this is to record the executable size ( which > > may change so this wont work either ) , and compare them, because even in an > > unsuccessful build an .exe is created of some size. > > > > Anyone have any ideas on how to test if a build succeeds ? Other than manually parsing the results ? > > > > C > > What about the return code? Every console application returns an integer to the shell. (this is how utilities like make know when to stop) > > -- andy > |
October 22, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to J Anderson | Another DIDE idea I was just thinking that would be cool: If you could link the DIDE with the newsreader, so you could send an email with an attachment of the code to the d newsgroup. That would make bug reporting (among other things) much easier. -Anderson |
October 22, 2003 Re: DIDE and compiler messages | ||||
---|---|---|---|---|
| ||||
Posted in reply to Charles Sanders | Charles Sanders wrote:
> NM i found it , changed news readers finnaly. Im using Free Agent what is
> everyone else using ?
>
> C
Mozilla Thunderbird but sometimes Gravity (both free of course :).
- John
|
Copyright © 1999-2021 by the D Language Foundation