On Fri, 17 Sep 1999 07:30:37 -0500, David Starner <[EMAIL PROTECTED]> wrote:
>On Fri, Sep 17, 1999 at 11:38:29AM +0100, Chris Rutter wrote:
>> On Thu, 16 Sep 1999, David Bristel wrote:
>> Yes, either this or a FIFO expiration policy on /var/cache/apt/packages
>> which gets automatically applied whe
On Thu, 16 Sep 1999 11:02:48 -0400, Chris Gorman <[EMAIL PROTECTED]> wrote:
>I was wondering if grep/fgrep/egrep are meant to be seperate programs
>or, hard links to one binary? If I take a long listing of the *ep files
>in /bin, they are all 47616 bytes, but they all only have one file
>link. Do
adjust existing code to the correct style.
It doesn't suggest any particular coding or testing techniques at all.
Other Linux documents describe procedures (e.g. how to prepare and
submit a patch) and technique (although defining coding technique in
a kernel is always approximate at best, and
han once because of multiply-defined enumerated
types. Or something, I forget what at the moment.
We decided that autoconf was better at that sort of thing anyway, and that
we should not be feeding 64-bit-unclean code to an Alpha.
--
Zygo Blaxell, Linux Engineer, Corel Corporation. [EMAIL PROTEC
In article <[EMAIL PROTECTED]>,
Zygo Blaxell <[EMAIL PROTECTED]> wrote:
Hmmm...somehow I dropped this text about checking things into a source
repository:
Many open-source projects do have public CVS repositories but
generally do not liberally hand out write access
In article <[EMAIL PROTECTED]>,
Oliver Elphick wrote:
>Zygo Blaxell wrote:
> >>10. Function/method size: bigger is not better. Functions and methods shoul
> >d
> >>be kept to a maximum of 40-50 lines. Larger methods should be broken down
> >>into
understand the rationale for this? egcs behaves identically
in both cases as far as I can tell.
Of course, missing from any Corel coding style document is a good set of
rules for making life easier for people who have to do ports, especially
those who cannot use Microsoft compilers for the target archi
7 matches
Mail list logo
