From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Microsoft C
Date: Sat, 26 Sep 2015 11:11:22 -0400 [thread overview]
Message-ID: <20150826111122.eklhad@comcast.net> (raw)
gcc allows us to define variables anywhere in a block, but Studio C does not.
In the interest of a possible windows port, I request all developers
keep variable definitions at the top of each function or block,
as per K&R.
I already do this, almost all the time,
but I slipped / forgot on a few occasions,
and I am fixing these now.
Karl Dahlke
next reply other threads:[~2015-09-26 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 15:11 Karl Dahlke [this message]
2015-09-26 15:36 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150826111122.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).