On Tue, 14 Dec 2004 14:21:40 -0800, Kevin Scaldeferri
<[EMAIL PROTECTED]> wrote:
> On Dec 14, 2004, at 2:10 PM, H.Merijn Brand wrote:
> > Yes. Ditch emacs. It knows only the *wrong* styles.
>
> uh... yeah... okay. You realize elisp is Turing-complete, right?
Um, yeah. Right. My cat is Turing
On Tue, 14 Dec 2004 23:10:51 +0100, H.Merijn Brand <[EMAIL PROTECTED]> wrote:
>
> Yes. Ditch emacs. It knows only the *wrong* styles.
>
Way to totally make a cogent argument. Next I suppose we'll hear about
how the Sun compilers totally pwn gcc2.
--
Shawn Boyette
<[EMAIL PROTECTED]>
H.Merijn Brand wrote:
Just only today I hit an M$Access database with a table named
`./onderw`.`"Bus"; "Taxi"; "Auto"`
My mail client inexplicably just quit. I assume because it was so
disgusted.
--
David Cantrell
On Dec 14, 2004, at 2:10 PM, H.Merijn Brand wrote:
On Tue 14 Dec 2004 21:49, Michael G Schwern <[EMAIL PROTECTED]> wrote:
Here's what I have to say about clever bracing/spacing styles.
Your bracing/spacing style should not be a detriment. It should not
be a limitation. If common editors have trou
On Tue, Dec 14, 2004 at 11:10:51PM +0100, H.Merijn Brand wrote:
> > If programmers outside your project look at it and go "Huh?" you've just
> > lost yourself a potential patch as they recoil.
>
> Don't think so. spaces and bracing is hard to do it so bad as to other people
> unable to be able to
On Tue 14 Dec 2004 21:49, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> Here's all I have to say about tabs.
>
> I expect the source to look the same no matter whose editor, pager, printer
> or utility I run it through. Literal tabs violate this. The end.
>
> Here's what I have to say about
Here's all I have to say about tabs.
I expect the source to look the same no matter whose editor, pager, printer
or utility I run it through. Literal tabs violate this. The end.
Here's what I have to say about clever bracing/spacing styles.
Your bracing/spacing style should not be a detrim
On Tue, Dec 14, 2004 at 11:15:13AM +, Ben Evans wrote:
> On Tue, Dec 14, 2004 at 05:35:53AM -0500, Michael G Schwern wrote:
> > Tripped across this on WardsWiki just now. #5 is my favorite as its often
> > forgotten in the noise.
"Oh, the noise! Oh, the noise! Noise! Noise! Noise!
That's one
On Tue 14 Dec 2004 18:21, Ricardo SIGNES <[EMAIL PROTECTED]> wrote:
> * "H.Merijn Brand" <[EMAIL PROTECTED]> [2004-12-14T11:28:19]
> > About spaces, another thing springs to mind, for which I would gladly kill
> > the
> > responsible people to allow it (I bet M$ was the first to push it): Spaces
* "H.Merijn Brand" <[EMAIL PROTECTED]> [2004-12-14T11:28:19]
> About spaces, another thing springs to mind, for which I would gladly kill the
> responsible people to allow it (I bet M$ was the first to push it): Spaces in
> database table and field names. DON'T! NEVER! Once you start it, you will
>
On Tue 14 Dec 2004 15:15, [EMAIL PROTECTED] (Dominic Mitchell) wrote:
> On Tue, Dec 14, 2004 at 12:21:50PM +, Matt Sergeant wrote:
> > On 14 Dec 2004, at 11:26, Clayton, Nik wrote:
> > >To be honest, I don't care if someone's house style is for TAB to
> > >indent
> > >2, 4, or 8 characters; ho
On Tue 14 Dec 2004 17:10, Adam Turoff <[EMAIL PROTECTED]> wrote:
> On Tue, 14 Dec 2004 16:14:32 +0100, H.Merijn Brand <[EMAIL PROTECTED]>
> wrote:
> > On Tue 14 Dec 2004 16:04, "Clayton, Nik" <[EMAIL PROTECTED]>
> > wrote:
> > > I've normally got enough going on in my head when writing code,
> > >
On Tue, 14 Dec 2004 16:14:32 +0100, H.Merijn Brand <[EMAIL PROTECTED]>
wrote:
> On Tue 14 Dec 2004 16:04, "Clayton, Nik" <[EMAIL PROTECTED]>
> wrote:
> > I've normally got enough going on in my head when writing code,
> > worrying about the house style should not be one of them.
>
> Wrong. It shoul
On Tue 14 Dec 2004 16:21, "Clayton, Nik" <[EMAIL PROTECTED]> wrote:
> > > I've normally got enough going on in my head when writing code, worrying
> > > about the house style should not be one of them.
> >
> > Wrong. It should be. You write, and someone else - or yourself - has to
> > maintain the
On Tue, Dec 14, 2004 at 02:15:45PM +, Dominic Mitchell wrote:
> On Tue, Dec 14, 2004 at 12:21:50PM +, Matt Sergeant wrote:
>> On 14 Dec 2004, at 11:26, Clayton, Nik wrote:
>>> That's something the editor can care about. When I hit the TAB key it
>>> should just do whatever the house style
> > I've normally got enough going on in my head when writing code, worrying
> > about the house style should not be one of them.
>
> Wrong. It should be. You write, and someone else - or yourself - has to
> maintain the code later. This means that you have to write with style and
> maintainabilit
On Tue 14 Dec 2004 16:04, "Clayton, Nik" <[EMAIL PROTECTED]> wrote:
> > I /think/ he means what the tab key's effect is when typed in
> > his editor of choice
>
> Correct. Hitting TAB should indent to the correct level for the current
> context. I don't especially care whether the editor does b
> I /think/ he means what the tab key's effect is when typed in
> his editor of choice
Correct. Hitting TAB should indent to the correct level for the current
context. I don't especially care whether the editor does by inserting
actual TAB characters or a bunch of spaces.
I've normally got eno
On 14 Dec 2004, at 11:26, Clayton, Nik wrote:
http://www.c2.com/cgi/wiki?UncleBobOnCodingStandards
On coding standards:
I'd add an additional:
* Make sure your tools enforce them, and make complying with them
as simple as possible.
To be honest, I don't care if someone's house style is for TA
On Tue, Dec 14, 2004 at 12:21:50PM +, Matt Sergeant wrote:
> On 14 Dec 2004, at 11:26, Clayton, Nik wrote:
> >To be honest, I don't care if someone's house style is for TAB to
> >indent
> >2, 4, or 8 characters; how much second level indentations are indented
> >by;
> >whether or not braces c
On Tue 14 Dec 2004 12:15, Ben Evans <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 14, 2004 at 05:35:53AM -0500, Michael G Schwern wrote:
> > Tripped across this on WardsWiki just now. #5 is my favorite as its often
> > forgotten in the noise.
> >
> > http://www.c2.com/cgi/wiki?UncleBobOnCodingStandard
> > http://www.c2.com/cgi/wiki?UncleBobOnCodingStandards
> >
> > On coding standards:
I'd add an additional:
* Make sure your tools enforce them, and make complying with them
as simple as possible.
To be honest, I don't care if someone's house style is for TAB to indent
2, 4, or 8 charact
On Tue, Dec 14, 2004 at 05:35:53AM -0500, Michael G Schwern wrote:
> Tripped across this on WardsWiki just now. #5 is my favorite as its often
> forgotten in the noise.
>
> http://www.c2.com/cgi/wiki?UncleBobOnCodingStandards
>
> On coding standards:
>
>1. Let them evolve during the first f
Tripped across this on WardsWiki just now. #5 is my favorite as its often
forgotten in the noise.
http://www.c2.com/cgi/wiki?UncleBobOnCodingStandards
On coding standards:
1. Let them evolve during the first few iterations.
2. Let them be team specific instead of company specific.
3. D
24 matches
Mail list logo
