Re: \x and strings
- From: "Martin Richter [MVP]" <martin.richter@xxxxxxxx>
- Date: Thu, 14 Apr 2005 13:13:17 +0200
Hallo John Carson!
"Martin Richter [MVP]" <martin.richter@xxxxxxxx> wrote in message news:d3laie$d1s$1@xxxxxxxxx
If it is a non-unicode string a\x01bc will do it.
If it is a unicode string use a\x001bc
Have you tried compiling this? (It doesn't compile for me.)
No. I am sorry about the wrong infos.
I just read the docs. And I thought that the parser stopped after 2 or 3 chars, becuase the docuemntation should explicitly 2 and 3 chars after \x. In fact it parses all chars unti it find a character not matching the sequence and this causes an overflow.
So the only way is what John Carson wrote.
-- Martin Richter [MVP] WWJD "In C we had to code our own bugs. In C++ we can inherit them." FAQ : http://www.mpdvc.de Samples: http://www.codeguru.com http://www.codeproject.com .
- Follow-Ups:
- Re: \x and strings
- From: Frank Hickman [MVP]
- Re: \x and strings
- References:
- \x and strings
- From: lallous
- Re: \x and strings
- From: Martin Richter [MVP]
- Re: \x and strings
- From: John Carson
- \x and strings
- Prev by Date: Create and share a directory
- Next by Date: Re: Create and share a directory
- Previous by thread: Re: \x and strings
- Next by thread: Re: \x and strings
- Index(es):
Relevant Pages
|
Loading