dev-cpp-users

[Dev-C++] Bloodshed or dev-c++ question

[Bob W. <bo...@ph...>]

Today I spend another marathon session trying to figure out why I could =
not get any console output from a program. I could go to a DOS window =
and type "newarray > test.txt" and the file created was exactly what I =
expected the console output to be. If I brought up the windows "close =
program" window by doing the Ctrl-Alt-Del trick, it would show that the =
program was still running, but the DOS window had returned to the =
command prompt.=20

This is the second time something like this has happened. In both cases, =
I had accidentally had selected a windows application in the new project =
window and then deleted the default "Untitled1.cpp" it created. That =
fill was filled with windows specific code. When I deleted that file, I =
thought I had fixed the problem, but I had not. I finally discovered =
that the code I had written was fine when I copied it to a different =
name and compiled it on a different compiler. I deleted the project, =
rsrc.o, and rsrc.rc files and returned to the dev-c++ environment. I =
created a new console project, compiled the code and it ran perfectly. =
Since this was the second time, you would think I would not have wasted =
a half a day solving it. The problem is insidious because it is hard, at =
least for me, to detect.=20

My request for assistance is this:

  1.. Is there an easier way to solve the problem other than deleting =
the files and starting over? In other words, is there a file I can check =
for a flag, etc?
  2.. Is there something that is easily identifiable that the Bloodshed =
IDE that would be an obvious clue that this is the problem?
Thanks,

Bob Wilson

RE: [Dev-C++] Bloodshed or dev-c++ question

[Ioannis V. <no...@ho...>]

 <http://run.to/noicys> 
-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of Bob
Wilson
Sent: Sunday, April 14, 2002 7:42 AM
To: Dev-C++ User Mailing List
Subject: [Dev-C++] Bloodshed or dev-c++ question



Today I spend another marathon session trying to figure out why I could
not get any console output from a program. I could go to a DOS window
and type "newarray > test.txt" and the file created was exactly what I
expected the console output to be. If I brought up the windows "close
program" window by doing the Ctrl-Alt-Del trick, it would show that the
program was still running, but the DOS window had returned to the
command prompt. 
 
 

newarrray > test.txt means output redirection. You redirect the output
to the file instead of the console.

 
 
This is the second time something like this has happened. In both cases,
I had accidentally had selected a windows application in the new project
window and then deleted the default "Untitled1.cpp" it created. That
fill was filled with windows specific code. When I deleted that file, I
thought I had fixed the problem, but I had not. I finally discovered
that the code I had written was fine when I copied it to a different
name and compiled it on a different compiler. I deleted the project,
rsrc.o, and rsrc.rc files and returned to the dev-c++ environment. I
created a new console project, compiled the code and it ran perfectly.
Since this was the second time, you would think I would not have wasted
a half a day solving it. The problem is insidious because it is hard, at
least for me, to detect. 
 
My request for assistance is this:
 

1.	Is there an easier way to solve the problem other than deleting
the files and starting over? In other words, is there a file I can check
for a flag, etc? 

2.	Is there something that is easily identifiable that the
Bloodshed IDE that would be an obvious clue that this is the problem? 

 
For simple console programs do not use projects. But if you wish to use
projects anyway, create a new console project and add your files there.
 
 
Ioannis

* Ioannis Vranos
* Programming pages: http://www.noicys.cjb.net
<http://www.noicys.cjb.net/> 
* Alternative URL: http://run.to/noicys

Re: [Dev-C++] Bloodshed or dev-c++ question

[Luigi S. <gi...@li...>]

At 23:41 13/04/02 -0500, Bob Wilson wrote:
>Today I spend another marathon session trying to figure out why ...

If you have so many problems, consider not using the IDE at all, the 
compiler can be used from the command line.

--
Luigi
gi...@li...

Re: [Dev-C++] Bloodshed or dev-c++ question

[Bob W. <bo...@ph...>]

>> If you have so many problems, consider not using the IDE at all, the  =
compiler can be used from the command line. <<

Because of three reasons. First, I do not know all of the compiler =
runtime calls. Second, it would take more time to learn them than to =
build my learning curve with dev-c++. Third, it is a pain to switch =
between a decent windows based editor and a DOS window.

Regards,

Bob Wilson

Re: [Dev-C++] Bloodshed or dev-c++ question

[Luigi S. <gi...@li...>]

Hello,

I do not know what "runtime calls" are, probably my computer knowledge is 
too limited, so excuse me if, only a newbie, I try to give some hint.

What I wanted to say (but I'm sure you already know it) is this: if I have 
some code in the file "hello.c" and wish to make the binary file, I type 
"gcc hello.c" and then just rename the file "a.exe" to something I like 
(perhaps hello.exe).

Of course I'm talking about console applications, since I do not know 
anything about Windows programming.

At 17:31 14/04/02 -0500, Bob Wilson wrote:
> >> If you have so many problems, consider not using the IDE at all, 
> the  compiler can be used from the command line. <<
>
>Because of three reasons. First, I do not know all of the compiler runtime 
>calls. Second, it would take more time to learn them than to build my 
>learning curve with dev-c++. Third, it is a pain to switch between a 
>decent windows based editor and a DOS window.
>
>Regards,
>
>Bob Wilson
>

--
Luigi
gi...@li...