putty-source/resource.h

//{{NO_DEPENDENCIES}}
// Microsoft Developer Studio generated include file.
// Used by win_res.rc
//

// Next default values for new objects
//
#ifdef APSTUDIO_INVOKED
#ifndef APSTUDIO_READONLY_SYMBOLS
#define _APS_NEXT_RESOURCE_VALUE        101
#define _APS_NEXT_COMMAND_VALUE         40001
#define _APS_NEXT_CONTROL_VALUE         1000
#define _APS_NEXT_SYMED_VALUE           101
#endif
#endif
Initial checkin: beta 0.43 [originally from svn r11] 1999-01-08 13:02:13 +00:00			`//{{NO_DEPENDENCIES}}`
			`// Microsoft Developer Studio generated include file.`
			`// Used by win_res.rc`
			`//`

			`// Next default values for new objects`
Whitespace rationalisation of entire code base. The number of people has been steadily increasing who read our source code with an editor that thinks tab stops are 4 spaces apart, as opposed to the traditional tty-derived 8 that the PuTTY code expects. So I've been wondering for ages about just fixing it, and switching to a spaces-only policy throughout the code. And I recently found out about 'git blame -w', which should make this change not too disruptive for the purposes of source-control archaeology; so perhaps now is the time. While I'm at it, I've also taken the opportunity to remove all the trailing spaces from source lines (on the basis that git dislikes them, and is the only thing that seems to have a strong opinion one way or the other). Apologies to anyone downstream of this code who has complicated patch sets to rebase past this change. I don't intend it to be needed again. 2019-09-08 20:29:00 +01:00			`//`
Initial checkin: beta 0.43 [originally from svn r11] 1999-01-08 13:02:13 +00:00			`#ifdef APSTUDIO_INVOKED`
			`#ifndef APSTUDIO_READONLY_SYMBOLS`
			`#define _APS_NEXT_RESOURCE_VALUE 101`
			`#define _APS_NEXT_COMMAND_VALUE 40001`
			`#define _APS_NEXT_CONTROL_VALUE 1000`
			`#define _APS_NEXT_SYMED_VALUE 101`
			`#endif`
			`#endif`