﻿id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
3966	Macro @WinLevel	Alecsis1		"Hi!
In ''addition'' to @OSVersion, let's call it for example @WinLevel
What's the difference.  @OSVersion returns _string_ value like 'WIN_XP', 'WIN_10' and so on. In some cases this is rather not convenient.
I'd like to suggest a macro returning _integer_ result to simplify native numeric comparison of OS versions.
For example:

{{{
@WIN_XP     ->  @WinLevel = 0x0501
@WIN_2003   ->  @WinLevel = 0x0502
@WIN_Vista  ->  @WinLevel = 0x0600
@WIN_7      ->  @WinLevel = 0x0601
@WIN_8      ->  @WinLevel = 0x0602
@WIN_81     ->  @WinLevel = 0x0603
@WIN_10     ->  @WinLevel = 0x0A00

}}}
… and so on; in addition the codes above correlate with results returned by WinAPI 

The similar codes may be used for server editions especially if there's no difference either it's server or it's ordinary PC
Thank you for attention!
PS1 May be better @OSLevel instead of @WinLevel?… 
PS2 As usual sorry for my weak English"	Feature Request	closed		AutoIt		None	Rejected		
