Menu
▾
▴
naviserver-devel
|
From: Zoran V. <zv...@ar...> - 2005-06-13 11:36:24
|
Hi ! I would like to see if we can agree on the style used when formatting source-code. What I find very annoying is the usage of the TAB. According to both AOL and TCL style-guides, the TAB is deprecated. Now, in the Tcl project, it is still used, which I do not really understand?? The problem with TAB's is: if you have some other TAB-width set then 8 spaces, the format looks pretty desperate and difficult to follow. OTOH, if you expand TABS to spaces, then normally you can read the code regardless of your current TAB width. I would suggest we avoid using TAB's for formatting and use plain spaces instead. I have setup this in emacs to expand TAB's to spaces always. What do you think? Zoran |
|
From: Vlad S. <vl...@cr...> - 2005-06-13 15:07:41
|
i agree Zoran Vasiljevic wrote: > Hi ! > > I would like to see if we can agree on the style used when > formatting source-code. > > What I find very annoying is the usage of the TAB. According > to both AOL and TCL style-guides, the TAB is deprecated. > Now, in the Tcl project, it is still used, which I do not > really understand?? > > The problem with TAB's is: if you have some other TAB-width > set then 8 spaces, the format looks pretty desperate and difficult > to follow. > OTOH, if you expand TABS to spaces, then normally you can read the > code regardless of your current TAB width. > > I would suggest we avoid using TAB's for formatting and use plain > spaces instead. I have setup this in emacs to expand TAB's to > spaces always. > > What do you think? > > Zoran > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office luge > track? > If you want to score the big prize, get to know the little guy. Play to > win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
|
From: Stephen D. <sd...@gm...> - 2005-06-14 07:31:41
|
On 6/13/05, Zoran Vasiljevic <zv...@ar...> wrote: > Hi ! >=20 > I would like to see if we can agree on the style used when > formatting source-code. >=20 > What I find very annoying is the usage of the TAB. According > to both AOL and TCL style-guides, the TAB is deprecated. > Now, in the Tcl project, it is still used, which I do not > really understand?? >=20 > The problem with TAB's is: if you have some other TAB-width > set then 8 spaces, the format looks pretty desperate and difficult > to follow. > OTOH, if you expand TABS to spaces, then normally you can read the > code regardless of your current TAB width. >=20 > I would suggest we avoid using TAB's for formatting and use plain > spaces instead. I have setup this in emacs to expand TAB's to > spaces always. >=20 > What do you think? I think this page needs some love: http://naviserver.sourceforge.net/wiki/index.php/Code_Standards |
|
From: Zoran V. <zv...@ar...> - 2005-06-14 07:37:13
|
Am 14.06.2005 um 09:31 schrieb Stephen Deasey: > > I think this page needs some love: > > http://naviserver.sourceforge.net/wiki/index.php/Code_Standards > And I think that you are absolutely great! Zoran |
|
From: Zoran V. <zv...@ar...> - 2005-06-14 08:12:20
|
Am 14.06.2005 um 09:31 schrieb Stephen Deasey: > > I think this page needs some love: > > http://naviserver.sourceforge.net/wiki/index.php/Code_Standards > > I will take the freedom to update each and every page I visit to conform to the code-style as above. I find the style pretty clean and simple and there should be no problems in following it. I will also add to the style-doc as I walk thru sources, if I find something missing or too ambiguous. Zoran |
|
From: Stephen D. <sd...@gm...> - 2005-06-15 07:06:39
|
On 6/14/05, Zoran Vasiljevic <zv...@ar...> wrote: >=20 > Am 14.06.2005 um 09:31 schrieb Stephen Deasey: >=20 > > > > I think this page needs some love: > > > > http://naviserver.sourceforge.net/wiki/index.php/Code_Standards > > > > >=20 > I will take the freedom to update each and every page I visit > to conform to the code-style as above. > I find the style pretty clean and simple and there should be > no problems in following it. I will also add to the style-doc > as I walk thru sources, if I find something missing or too ambiguous. Well, I don't know that the doc is perfect... I've imported the nsexample module into CVS: http://cvs.sourceforge.net/viewcvs.py/naviserver/modules/nsexample/ I think we should make nsexample more of a template for reuse, and make the Code Standards document more How and Why. We'd remove the template Makefile and header etc. |
|
From: Zoran V. <zv...@ar...> - 2005-06-15 07:10:41
|
Am 15.06.2005 um 09:06 schrieb Stephen Deasey: > I think we should make nsexample more of a template for reuse, and > make the Code Standards document more How and Why. We'd remove the > template Makefile and header etc. > Why would you remove the Makefile/header? OK, those are not code-style directives but are helpful for module writers. Zoran |
|
From: Stephen D. <sd...@gm...> - 2005-06-15 07:24:04
|
On 6/15/05, Zoran Vasiljevic <zv...@ar...> wrote: >=20 > Am 15.06.2005 um 09:06 schrieb Stephen Deasey: >=20 > > I think we should make nsexample more of a template for reuse, and > > make the Code Standards document more How and Why. We'd remove the > > template Makefile and header etc. > > >=20 > Why would you remove the Makefile/header? OK, those are not code-style > directives but are helpful for module writers. I think nsexample should become the template. New module writers would simply copy the whole thing into a new directory and start editing. |
|
From: Zoran V. <zv...@ar...> - 2005-06-15 07:40:28
|
Am 15.06.2005 um 09:23 schrieb Stephen Deasey: >> Why would you remove the Makefile/header? OK, those are not code- >> style >> directives but are helpful for module writers. >> > > > I think nsexample should become the template. New module writers > would simply copy the whole thing into a new directory and start > editing. > OK. This makes sense. Zoran |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X