X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: attaching source code to the ececutable
Date: 5 Feb 2004 14:06:11 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 22
Message-ID: <bvtikj$4lk$2@nets3.rz.RWTH-Aachen.DE>
References: <20040205052923 DOT 26490 DOT 00001487 AT mb-m07 DOT aol DOT com>
NNTP-Posting-Host: ac3b07.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1075989971 4788 137.226.33.205 (5 Feb 2004 14:06:11 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 5 Feb 2004 14:06:11 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Sterten <sterten AT aol DOT com> wrote:

> I usually attach my source code to the executable (type xxx.c >> xxx.exe)
> but haven't seen thisdone  by others. Why not ? 

Because it's a rather pointless exercise.  Not to mention that the
majority of serious C programs are built from quite a lot more than a
single source file, so this technique would fail anyway.  And then
there's programs that use pasting of data after the end of the .exe
file for storing *other* data (e.g. Allegro inlines .dat files).

> Are there disadvantages ?

There are, more to the point, no advantages.

> Shouldn't it be supported by the compiler and maybe even be the default ?

Definitely not.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.