Re: [gobo-eiffel-develop] Developer Guidelines (first draft)

[Berend de B. <be...@po...>]

Eric Bezault <er...@go...> writes:

>   The comb structure uses indentation, achieved through tab
>   characters (*not* spaces, which are messy, error-prone, and
>   not reader-parameterizable).

they're not parameterizable with every reader, so they look strange in
certain cases. And perhaps they are in ISE's IDE, but haven't detected
that option...

> From what I can see, it seems that the size of tabs used in 
> examples in OOSC2 is 4.

Hmm, I think it's 6 or perhaps just some xx em, not really clear.


> Then I don't see where the problem is. You can convert
> tabs to 3 spaces when you load the Eiffel class into Emacs,
> and convert them back to tabs when you save the file.

Then I don't see where the problem is. You can convert 3 spaces to
tabs when you load the Eiffel class into vim, and convert them back to
tabs when you save the file :-))

The point is that sometimes you have tabs in the file, sometimes
not. Not all editors handle tabs great, so just do away with them.

I agree that your source code works fine with tabs, but most others
don't. Take the SmallEiffel code, take EXML, take whatever source file
you might lay your hands upon.

But whatever we decide, what are our options to guarantee it is done
consistently? At check-in, cron job, code review??

Groetjes,

Berend. (-: