getline bug

[Jason Pursell]

I hope someone can tell me the reason that Microsoft hasn't fixed the
getline bug. The getline function in the header <string> has a problem if
you just want to read up to the newline. If you want to read up to some
other character it works. the knowledge base article:
http://support.microsoft.com/support/kb/articles/Q240/0/15.ASP
explains how to fix this behavior by modifying the header. It does fix the
problem.

I was wondering if the fix is worse than the original bug. In other words,
is the fix going to cause any other problems? If the fix is so easy, then
why hasn't Microsoft fixed it? Is it because it will cause other problems?

Thank you for your responses...
--
Jason Pursell
jpur...@nwlink.com

[Richard Norman]

"Jason Pursell" <jpur...@nwlink.com> wrote in message
news:uqqbdOG...@cppssbbsa02.microsoft.com...

This is one of the fixes included in the Dinkum patches found at
http://www.dinkumware.com/vc_fixes.html

[Jason Pursell]

Thank you very much.

That page is very informative and will be extremely useful.

Thank you, thank you, thank You...

Jason Pursell
jpur...@nwlink.com

[Robert Marshall]

> In article <ZK0H5.247$Zx.8...@typhoon.mw.mediaone.net>,
"Richard Norman" <rsno...@mediaone.net> writes:

RN> "Jason Pursell" <jpur...@nwlink.com> wrote in message
RN> news:uqqbdOG...@cppssbbsa02.microsoft.com...

>>
> I hope someone can tell me the reason that Microsoft hasn't fixed
> the getline bug. The getline function in the header <string> has a
> problem if you just want to read up to the newline. If you want to
> read up to some other character it works. the knowledge base
> article:
> http://support.microsoft.com/support/kb/articles/Q240/0/15.ASP
> explains how to fix this behavior by modifying the header. It does
> fix

RN> the

> problem.
>>
> I was wondering if the fix is worse than the original bug. In other
> words, is the fix going to cause any other problems? If the fix is
> so easy, then why hasn't Microsoft fixed it? Is it because it will
> cause other

RN> problems?

>>
> Thank you for your responses... -- Jason Pursell
> jpur...@nwlink.com
>>

RN> This is one of the fixes included in the Dinkum patches found at
RN> http://www.dinkumware.com/vc_fixes.html

I've looked at these changes and tried to apply the string::getline fix
but without success, I've tried complete rebuilds, rebuilding other
libraries used by my code, deleting any .pch files I could find.
Is there anything else obvious that I've still missed?

Robert
--
Robert Marshall (remove SPAM.NUNQUAM to reply)
Conformity means death for
any comunity. A loyal opposition is a necessity in any community
Karol Wojtyla (1969)

[Jason Pursell]

I made the change to the <string> library only ( no .h). It is literally
just four characters to change. I saved the <string> header and the bug
disappeared.

--
Jason Pursell
jpur...@nwlink.com

[Erik Funkenbusch]

"Robert Marshall" <ra...@SPAM.NUMQUAM.fsmail.net> wrote in message

> RN> This is one of the fixes included in the Dinkum patches found at
> RN> http://www.dinkumware.com/vc_fixes.html
>

> I've looked at these changes and tried to apply the string::getline fix
> but without success, I've tried complete rebuilds, rebuilding other
> libraries used by my code, deleting any .pch files I could find.
> Is there anything else obvious that I've still missed?

Yes, you have to build with the static library version of the CRT. The DLL
version does not get recompiled when you make these changes, and recompiling
the DLL would be bad anyways, since there would be no way to verify that the
version of the DLL you are using is the correct one on any given machine
(changing the version number might work, but you can't be sure MS won't come
out with the same version). And more importantly, you'll be changing the
semantics of other programs that rely on that library.