Xref: news-dnh.mv.net comp.os.msdos.djgpp:142
Path: news-dnh.mv.net!mv!news.sprintlink.net!news.bluesky.net!news.mathworks.com!news.kei.com!simtel!harbinger.cc.monash.edu.au!wilma.eng.monash.edu.au!junaid
From: junaid AT wilma DOT eng DOT monash DOT edu DOT au (Junaid A. Walker)
Newsgroups: comp.os.msdos.djgpp
Subject: VOTE: CODE STANDARDS
Date: 6 Jun 1995 11:26:24 GMT
Organization: Monash University
Lines: 62
Nntp-Posting-Host: wilma.eng.monash.edu.au
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp


On Tue, 6 Jun 1995, Eli Zaretskii wrote:
> > 	Junaid wrote;
> >	Goody, because you wont mind me commenting on the coding
> > style of go32 and friends. Please dont take offence, just my humble
> > opinions.
> 
> Why was it necessary to send this to the entire DJGPP public?  Wasn't

	Well since it concerns djgpp in general then it goes to all
concerned.

> private mail to DJ enough?  Critics on the coding style is as close to
> personal as you can get with programmers, don't you think?

	Not really (i was appologetic in the original message).
Only DJ's ideas of coding style differ from mine, like your hair color
is different. Maybe you might like my hair color, and get your
hair dyed. No big deal. Just maybe we can both be happy.

> 
> And besides, with all the DJGPP coding work DJ does entirely voluntarily,
> one wonders where does he get time to breathe, let alone adding comments
> to code.  (Did you know his wife gave birth to a boy about 3 weeks ago?)
> 

	Well still doesnt change the facts - the code is basically
undocumented, and has been that way since day one. Maybe its time
we started documenting things (emx is a good example). Sure if we
turn a blind eye to the state of the code, we'll all be fatter
and happier, but
i think we have to face the fact (esp if he has a newborn) that
dj will not be with us forever.

	Remeber standards work. The unspoken word and anarchy
disintegrate rapidly. Who cares about dj anyway, he develops djgpp
for his own personal interest, not for yours and not form mine.
His stance is politically correct; i do it for fun, if you want to
do things better, do it yourself. Enter me, i want to use djgpp
for real work. Hence i want the greatest milage possible; unfortunately
there are no roadmaps, and the path has washed away. Hopefully dj
can guide the djgpp comunity enough that it can stand on its own
feet.

	Also as i previous indicated, documentation tends, in the
long run, to reduce design/test/debug/developer time. Since dj is
obviously with djgpp for the long run, he might consider this.
As for new comers (like myself, on and off the last few years),
we should definitely be concerned about this issue. But this stigmatic
issue has never been discussed before. A tradegy. Just be objective,
and decide whatever you think is most beneficial.

	It would be wise to put it to a vote; "does djgpp need some
coding standards?". Any self respecting programmer would have to
agree. Even demo coders have standards (and commented code i must
add) ....


	Cheers,
	Junaid