«

This thing is driving me nuts.

why would a simple output file stream like this:

ofstream ofs;
ofs.open("c:\temp\somefile.txt")

set the fail bit?

calling ofs.fail() right after the open is returning true.

Hi,

\t
means tabstop
use either
c:/temp/somefile.txt
or
c:\\temp\\somefile.txt

--


Regards, Ron AF Greve

http://moonlit.xs4all.nl

"Dilip" <> wrote in message
news: oups.com...
>
> This thing is driving me nuts.
>
> why would a simple output file stream like this:
>
> ofstream ofs;
> ofs.open("c:\temp\somefile.txt")
>
> set the fail bit?
>
> calling ofs.fail() right after the open is returning true.
>

Moonlit wrote:
> Hi,
>
> \t
> means tabstop
> use either
> c:/temp/somefile.txt
> or
> c:\\temp\\somefile.txt

That was just an example. I know a backslash inside a string needs to
be escaped. The file does get created. Its just that I can't write
anythng into it because fail() returns true and I can't figure out why.
The low level OS _open (or whatever) call seems to successfully create
the file everytime. Somewhere after that I don't know why that bit is
getting set.

Dilip wrote:
> This thing is driving me nuts.
>
> why would a simple output file stream like this:
>
> ofstream ofs;
> ofs.open("c:\temp\somefile.txt")

Will Windoze let you put tabs in a file name? Remember
\ is special in C++.

Hi,

You should post the code that you used not something you made up.

The code you posted doesn't work neither on windows nor unix/linux

If you want help post your complete code cut and paste.

--


Regards, Ron AF Greve

http://moonlit.xs4all.nl

"Dilip" <> wrote in message
news: ups.com...
>
> Moonlit wrote:
>> Hi,
>>
>> \t
>> means tabstop
>> use either
>> c:/temp/somefile.txt
>> or
>> c:\\temp\\somefile.txt
>
> That was just an example. I know a backslash inside a string needs to
> be escaped. The file does get created. Its just that I can't write
> anythng into it because fail() returns true and I can't figure out why.
> The low level OS _open (or whatever) call seems to successfully create
> the file everytime. Somewhere after that I don't know why that bit is
> getting set.
>

Dilip wrote:
> This thing is driving me nuts.
>
> why would a simple output file stream like this:
>
> ofstream ofs;
> ofs.open("c:\temp\somefile.txt")
>
> set the fail bit?
>
> calling ofs.fail() right after the open is returning true.

If you create the file successfully, assuming the OS perimissions are
set appropritely, you should be able to stream to the file. But since
you aren't showing how you do that, nobody can help.

On Oct 26, 5:54 pm, "Salt_Peter" <pj_h...@yahoo.com> wrote:
> Dilip wrote:
> > This thing is driving me nuts.
>
> > why would a simple output file stream like this:
>
> > ofstream ofs;
> > ofs.open("c:\temp\somefile.txt")
>
> > set the fail bit?
>
> > calling ofs.fail() right after the open is returning true.If you create the file successfully, assuming the OS perimissions are
> set appropritely, you should be able to stream to the file. But since
> you aren't showing how you do that, nobody can help.

I am not streaming to the file yet. Before I decide to do that I do a
check to see if the stream is in usable state by calling ofs.fail().
Because fail() is returning true I am not going ahead with the
streaming. I am trying to figure why fail() returns true when the file
got created successfully.

On Oct 26, 5:30 pm, Ron Natalie <r...@spamcop.net> wrote:
> Dilip wrote:
> > This thing is driving me nuts.
>
> > why would a simple output file stream like this:
>
> > ofstream ofs;
> > ofs.open("c:\temp\somefile.txt")Will Windoze let you put tabs in a file name? Remember
> \ is special in C++.

That was just a typo in the example. The real code gets the file name
from elsewhere. As I repeatedly stated in other threads the file
*does* get created successfully right after the .open call. I just
don't understand why fail() on the stream returns true after that.

On 26 Oct 2006 15:27:20 -0700 in comp.lang.c++, "Dilip"
<> wrote,
>That was just an example. I know a backslash inside a string needs to
>be escaped.

Then it's not a very good example, is it?

> The file does get created. Its just that I can't write
>anythng into it because fail() returns true and I can't figure out why.

What does perror() say?

On Oct 26, 7:36 pm, David Harmon <sou...@netcom.com> wrote:
> On 26 Oct 2006 15:27:20 -0700 in comp.lang.c++, "Dilip"
> <rdil...@lycos.com> wrote,
> > The file does get created. Its just that I can't write
> >anythng into it because fail() returns true and I can't figure out why.

> What does perror() say?

Doesn't perror write to stderr? My app is not a console application.
Is there any other way to check? Or should I redirect stderr to
elsewhere and track down the error message? That seems awfully
complicated.