Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.c Subject: Re: Naming convention for structs and types Date: Wed, 18 Jan 2017 08:03:05 +1300 Lines: 24 Message-ID: References: <13ae9e88-30fd-4c3d-9427-51eea224fa77@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net E/s2YkFkboU2mtfdRKq7bAljutSDLb4YO+haQjgpoyF+GYY7k4 Cancel-Lock: sha1:MKmqBqw6jb14B/+FMMDUHzzrIhk= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: Xref: csiph.com comp.lang.c:102064 On 01/17/17 09:47 PM, Richard Heathfield wrote: > On 17/01/17 07:57, Ian Collins wrote: >> On 01/17/17 09:19 AM, Rick C. Hodgin wrote: >>> On Friday, January 13, 2017 at 1:31:02 AM UTC-5, Ian Collins wrote: >>>> On 01/13/17 08:58 AM, Rick C. Hodgin wrote: >>>>> I use the SWhatever because it's a convention in C++ to use CWhatever >>>>> for classes. >>>> >>>> No it isn't a convention, it is an artifact of MFC naming many of us C++ >>>> programmers despise. >>> >>> I was wondering why many C++ developers despise that naming convention. >>> To me it seems fundamental, such that it gives a cue on use as to exactly >>> what it is. >> >> The context should make it obvious what it is! > > I learned to avoid them when I discovered that you couldn't have a CList > of CLists. Did they ever fix that? In MFC? No idea, I've managed to avoid it! -- Ian