CompuServe Messages

#Small code

    11-Dec-87 14:49:38
Sb: #97728-#Small code
Fm: Paul Montgomery 71500,3525
To: Glenn Nielsen 75115,444
Glenn, Agreed, it is up to the individual programmer to determine the techniques that are usable in their particular situation. But, without knowledge of as many of the techniques as possible, How can he/she make a decision as to which one is applicable. What I was looking for was a source for as many ideas as possible as to how one can tailor the environment one is running in, to optimize it. ( for speed, size, ease of maintenance, or whatever applies. ) The information I had in hand was not understood by myself well enough to take full advantage of it. I hoped that this forum would be a source of ideas that I could experiment with to see if they were useable in different projects I am involved in. ( and it has. ). My understanding of those techniques ( with your help ) has grown considerably, but I still have a few questions. For instance, on disk 4 extras/tricks/avail.c in the compile string at the head of the file an assignment of DEFINE _stdout=_echo is made. What is _echo ? Also if you get the chance to download small.arc, in small6.map there are two other bits of code pulled in that I dont know why they are there or where they come from. Any ideas. Thanks for all of the help Paul