Welcome to the Lounge

Mycroft Holmes wrote:

As the lead developer I set the standards and if I find someone has reformatted my code I get quite grumpy

Joan M wrote:

And of course this doesn't allow any debate. I'm right. Anyone thinking a different thing must be burnt in fire.

Daniel Pfeffer wrote:

usually mandated by anal-retentive bosses

Daniel Pfeffer wrote:

The only problem with using tabs as a formatting mechanism is when reading code in a different editor, whose tab setting differs. Your nicely (and carefully) formatted code then looks like a formatting disaster.

Jeremy Falcon wrote:

So, I'm curious to know, what do y'all use still and why?

1. The IDE creates appropriate indentation when I hit the tab key
2. The IDE is smart enough to un-indent the entire group of spaces when I hit the delete key anywhere in the indented region (this is extremely rare, which is why I prefer tabs over spaces)
3. The IDE supports block indent \ un-indent
4. The IDE supports a "format" which will format the entire code block/file to however I've set up my IDE. 95% of the time I love how pressing '}' will reformat the C# / Javascript code.

1. C# using (and other language equivalents) should be in alphabetic order, unless, like in some other languages, they are imports that have dependencies on prior imports
2. .NET framework using's come first.
3. Third party using's are alphabetically grouped next, with a blank line between them and the .NET using's above.
4. Internal library using's next, grouped and separated as #2
5. Application specific using's next, same
6. One class per file
7. Methods separated by a single blank line
8. Public events first, one per line, the group "guarded" by a blank line.
9. Public properties next, one per line, the group "guarded" by a blank line.
10. Protected/private properties next, one per line, the group "guarded" by a blank line.
11. Internal fields next, one per line, the group "guarded" by a blank line.
12. Public constructors next, each constructor method separated by a single blank line.
13. Protected/private constructors next, each constructor method separated by a single blank line.
14. Public methods next, each constructor method separated by a single blank line.
15. Protected/private methods next, each constructor method separated by a single blank line.

$!	Run the Machine
$
$	offset = 0
$loop2:
$	input = f$extract(offset,1,p2)
$	if f$type(TM_'state'_'input') .eqs. "" then goto eoloop2
$
$	output = f$element(2,",",TM_'state'_'input')
$	move   = f$element(3,",",TM_'state'_'input') 
$	state  = f$element(4,",",TM_'state'_'input') 
$
$	p2['offset',1] := 'output'
$
$	if move .eqs. "-"
$	 then 
$	   if offset .eq. 0
$	    then p2 = "_" + p2
$	    else offset = offset - 1
$	    endif
$	 else
$	   offset = offset + 1
$	   if offset .eq. f$length(p2) then p2 = p2 + "_"	
$	 endif
$
$	goto loop2
$eoloop2:
$
$	write sys$output p2
$
$	goto end

(somecontrol.text = float.Parse(x) * float.Parse(y)).ToString();