Mail Archives: djgpp/1999/06/26/17:26:53
In article <E1E66A72052F046F DOT 7E638B1C551D6768 DOT 8D8331868A41F789 AT lp DOT airnews DOT net>, "jdm" <jdm1intx AT DIE_SPAMBOT_DIEairmail DOT net> wrote:
..
>it. I agree it would be nice to have a nice installation program or a
>step-by-step list that brings all the various issues involved in
>installing and getting djgpp/rhide to work into a single easy-to-read
>document. Unfortunately, UNIX guys (or gals) are incapable of
>comprehending the concept of "easy-to-read". They like to hide
>everything in paragraphs and paragraphs of obfuscated techno-babble to
>impress the world with the size of their temporal lobes.
>
>jdm
>
>
>
I whish I could tell you, that you were wrong, but I can't, because you are
not. Not quite, at least. I see you point.
I also see DJ's point and it amazes me time and time again to see people that
are willing to go through the effort of learning C or C++, but who seem very
reluctant to spent a few hours to find out where and how to find information
for their problems. After all learning to program is a long term project, and
to master it, you will have to know your compiler and editor/IDE very well.
Before this is getting even lengthier: Why don't you go ahead and write a
little readme that does what you want? You seem to be somebody who has the
necessary amount of knowledge (which has absolutely nothing to do with the
size of your temporal lobes), but at the same time can remember the problems a
newbie has.
PS: Why is rhide always treated like a integral part of DJGPP? As good as it
is, it is just an add-on and nobody is required to download it and work with
it. So one cannot expect to find instructions on setting up rhide in the
readme.1st for djgpp.
--
Manni
- Raw text -