From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Compilation in C and ADA
Date: Sat, 23 Jul 2016 22:08:28 +0200 [thread overview]
Message-ID: <86lh0syv5v.fsf@student.uu.se> (raw)
In-Reply-To: mailman.1937.1469296394.26859.help-gnu-emacs@gnu.org
Dale Snell wrote:
> You could create a Makefile that will call
> your compiler, but for a single file project
> that's a bit of overkill, IMO.
It is a good idea to have a Makefile even for
the short time when the project consists of
a single file, because even the smallest
project get by this state very fast, and if
there isn't a Makefile, the programmer may be
hesitant to split the program into two files
even when it is natural as this will imply the
extra work of setting up a Makefile.
It is good to do it day one and be done
with it!
With C, obviously there are the header files,
but even in Ada, IIRC from my schoolbook
experience of the language you'd similarly put
"definitions" in one file, and "implementations"
in a corresponding?
--
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
- so far: 58 Blogomatic articles -
next prev parent reply other threads:[~2016-07-23 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 11:11 Compilation in C and ADA Edward Zacharek
2016-07-19 17:36 ` B.V. Raghav
2016-07-20 2:50 ` Francis Belliveau
2016-07-20 4:30 ` B.V. Raghav
2016-07-23 14:22 ` Francis Belliveau
2016-07-23 17:52 ` Dale Snell
[not found] ` <mailman.1937.1469296394.26859.help-gnu-emacs@gnu.org>
2016-07-23 20:08 ` Emanuel Berg [this message]
[not found] ` <mailman.1922.1469283823.26859.help-gnu-emacs@gnu.org>
2016-07-23 15:05 ` Emanuel Berg
2016-07-24 4:20 ` Francis Belliveau
[not found] ` <mailman.1955.1469334108.26859.help-gnu-emacs@gnu.org>
2016-07-24 12:48 ` Emanuel Berg
2016-07-23 16:23 ` Kendall Shaw
[not found] <mailman.1680.1468936015.26859.help-gnu-emacs@gnu.org>
2016-07-20 3:43 ` Rusi
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=86lh0syv5v.fsf@student.uu.se \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.