Re: LPCSTR

Article View: borland.public.cppbuilder.nativeapi

Article #10086

Back to borland.public.cppbuilder.nativeapi Previous Next

#10086

From: Sten Larsson
Date: Thu, 13 May 2004 10:04

16 lines
1260 bytes

"Ed Mulroy [TeamB]" wrote:

>const char* for LPCSTR
>char * for LPSTR
>
>I don't see a reason to use LPCSTR in Windows code.  I use const char

Good - I'm not alone. I just started thinking - maybe there is
something I miss by not using LPVOID, LPCSTR, LPBYTE or whatever they
are named. Been reading lots of examples lately :-)

Thanks!

/sten
---
For direct email, remove _ and X.

Technical Details

Message-ID: <7th6a016m45bf5mmc0njnup4e1v609qk4j@4ax.com>

Path:

arc1-ca.pugleaf.net!controlnews3.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

References: <7q66a01vald1j2ckj6ghu88ud9c9rim712@4ax.com> <40a31e61$1@newsgroups.borland.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10cc67,87911e32b3c1490e
X-Google-Attributes: gid10cc67,public
From: Sten Larsson <s_t_enX@Xs_ten_l.com>
Newsgroups: borland.public.cppbuilder.nativeapi
Subject: Re: LPCSTR
Date: Thu, 13 May 2004 03:04:27 -0700
Message-ID: <7th6a016m45bf5mmc0njnup4e1v609qk4j@4ax.com>
References: <7q66a01vald1j2ckj6ghu88ud9c9rim712@4ax.com> <40a31e61$1@newsgroups.borland.com>
X-Newsreader: Forte Agent 1.91/32.564
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 66.81.64.70
X-Trace: newsgroups.borland.com 1084442978 66.81.64.70 (13 May 2004 03:09:38 -0700)
Lines: 16
Path: arc1-ca.pugleaf.net!controlnews3.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Reply to Parent Message