Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!border2.nntp.ams1.giganews.com!nntp.giganews.com!buffer2.nntp.ams1.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 14 Jan 2017 08:12:59 -0600
From: Gareth Owen <gwowen@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Naming convention for structs and types
References: <f491ab71-d445-4044-81ac-2819a4726b29@googlegroups.com> <13ae9e88-30fd-4c3d-9427-51eea224fa77@googlegroups.com> <edraguF4adcU2@mid.individual.net> <o5aith$qv9$1@dont-email.me> <c2873081-2433-4659-a3a0-d1e74d76801d@googlegroups.com> <o5b7hn$4qe$3@dont-email.me> <5f80f737-f90a-41c9-9ffd-b82ae919840d@googlegroups.com> <edt0kvF4adeU2@mid.individual.net> <o5biiv$sr3$1@dont-email.me> <edt21cF4adeU4@mid.individual.net> <o5bt2d$ul1$1@dont-email.me> <87fuklq3rz.fsf@gmail.com> <o5d33p$ma6$1@dont-email.me> <o5d8if$781$1@dont-email.me> <877f5xpy9h.fsf@gmail.com> <o5daqr$ehj$1@dont-email.me>
Date: Sat, 14 Jan 2017 14:12:59 +0000
Message-ID: <87sholafx0.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Cancel-Lock: sha1:fjkgJq2DKZLwnQb/U+MQUvQSMq8=
MIME-Version: 1.0
Content-Type: text/plain
Lines: 9
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-qVfso3rHHsOQVuEOlUMH9GM3B7d3Ks0kEQ/qkOFMWnLd49Lc2G3zwqxQLKOM0Iv0OwpylU/EANDSGZP!Z3uLYjq/EhI442QiYjUYhRn803pJHFnKJjkZjRO42ItaE2OIw1nA2PBVQRMMzPAw8wxELA==
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1832
Xref: csiph.com comp.lang.c:101758

BartC <bc@freeuk.com> writes:

> (Nice touch BTW of having .cc meaning a C++ source file, and cc
> meaning a C compiler. You don't want to make this stuff too obvious!)

I use .cpp exclusively.
Nevertheless .cc meaning C++ is incredibly common.

That you've never seen it before is ... unremarkable.