Re: Dangerous behavior of CString

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jos Groot Lipman <dontspam@xxxxxxx>
Date: Fri, 6 Jan 2006 14:52:04 +0100

> > str += "world."; // 8-bit string!!
>
> You omitted the _T() macro in a place where you did need it.

He is aware of that and willing to change it. But he was hoping that the compiler would find
this 'error' for him which it did not.

Jos
.

Follow-Ups:
- Re: Dangerous behavior of CString
  - From: David Wilkinson

References:
- Dangerous behavior of CString
  - From: David Wilkinson
- Re: Dangerous behavior of CString
  - From: Norman Diamond

Prev by Date: Re: How to change the font while window is loaded.. ??
Next by Date: Re: How to change the font while window is loaded.. ??
Previous by thread: Re: Dangerous behavior of CString
Next by thread: Re: Dangerous behavior of CString
Index(es):
- Date
- Thread

Relevant Pages

-D_FILE_OFFSET_BITS=64 where to put it in a make project ?
... I need to pass the compiler the macro above but I really don't know ... a GTK2 only archive manager - ... Prev by Date: ...
(comp.os.linux.development.apps)
Re: Good C programming style
... _name are reserved for compiler; i don't like thid kind of macro ... Prev by Date: ...
(comp.lang.c)
Re: -D_FILE_OFFSET_BITS=64 where to put it in a make project ?
... > I need to pass the compiler the macro above but I really don't know ... What you really want is the AC_SYS_LARGEFILE macro, ... Roger Leigh ... Prev by Date: ...
(comp.os.linux.development.apps)
Re: optimizing lisp - best practices?
... > The generated code using this macro is still quite ugly but, ... > will be optimized by every compiler to ... (defmacro power-pretty (x n) ... Prev by Date: ...
(comp.lang.lisp)
Re: Question about compilation/evaluation environments
... I guess it depends on what you mean by evaluating some code. ... In this case, the form is the macro function, aka macro ... invocation of compiled code produced by a compiler. ... ANY OF THESE FACILITIES MIGHT SHARE THE SAME EXECUTION ...
(comp.lang.lisp)