Help topic "f_wininfo.htm" - a nit

[Steve Fabian]

Since TCC.EXE is restricted to Intel/AMD architectures, %@WININFO[1] can
return only codes 0 or 9. All other values ought to be deleted or marked as
not implemented.
--
Steve

 

[rconn]

Since TCC.EXE is restricted to Intel/AMD architectures, %@WININFO[1] can return only codes 0 or 9. All other values ought to be deleted or marked as not implemented.

It can also return 6.

 

[Steve Fabian]

rconn wrote:

| Quote:
| Originally Posted by Steve Fábián
|| Since TCC.EXE is restricted to Intel/AMD architectures,
|| %@WININFO[1] can return only codes 0 or 9. All other values ought to
|| be deleted or marked as not implemented.
|
| It can also return 6.

Regardless, the values that the TCC variable function can actually
return ought to be distinguishable from values the underlying API can return
when it is run on a platform where TCC is unavailable.
--
Steve

 

[Steve Fabian]

rconn wrote:

| Quote:
|| Regardless, the values that the TCC variable function can
|| actually return ought to be distinguishable from values the
|| underlying API can return when it is run on a platform where TCC
|| is unavailable.
|
| There is no platform where the underlying API can be run that
| doesn't also support TCC.

Well, maybe I used the wrong term ("underlying API"). What I ought to
have requested was that the list enumerate only the actual range of the TCC
function %@WININFO[1], i.e., the set of values it can actually return.
Values indicating platforms where TCC will not run, if included at all,
should be distinguishable from the actual range. When one writes a program
to translate from the function's numeric value to a platform description
only the actual range is relevant.
--
Steve