From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <871ur47qu3.fsf@gmail.com> References: <86vcoif5f4.fsf@cmarib.ramside> <871ur47qu3.fsf@gmail.com> Date: Thu, 12 Jan 2012 15:07:01 -0800 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Plan 9/plan9port coding conventions Topicbox-Message-UUID: 59da8dd6-ead7-11e9-9d60-3106f5b1d025 i was providing the example to what John was pointing out about the futility of including type information in identifiers when there isn't an enforcement mechanism. in this case, presumably the variable named pszBesmirchesAllHungariansEverywhereNotation is a 'pointer to zero terminated string ...', which it clearly isn't. I don't mind the mixed case names and the names in the main Go packages seem very reasonable and easy to remember. -Skip On Thu, Jan 12, 2012 at 9:56 AM, Christian Neukirchen wrote: > quanstro@quanstro.net (erik quanstrom) writes: > >> On Wed Jan 11 20:34:39 EST 2012, skip.tavakkolian@gmail.com wrote: >>> by way of an example: >>> >>> int pszBesmirchHungeriansNotation; >> >> who let the camel's nose in the tent? > > The Go people. > > -- > Christian Neukirchen =A0 =A0http://chneukirchen.o= rg >