Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Inkey(0)
45 views
Skip to first unread message
Gerard de Vries
Jun 1, 2012, 5:34:19 AM6/1/12
to
Hi,
In the past, it was recommended to not use inkey(0) cause it would increase
CPU usage significantly. I wonder if that's still true, or that it only
applied to Clipper (5.2). Can anyone shed some light on this please?
Thanks.
Gerard
In the past, it was recommended to not use inkey(0) cause it would increase
CPU usage significantly. I wonder if that's still true, or that it only
applied to Clipper (5.2). Can anyone shed some light on this please?
Thanks.
Gerard
dlzc
Jun 1, 2012, 10:18:56 AM6/1/12
to
Dear Gerard de Vries:
Does not apply to (x)Harbour.
Does not apply to Clipper 5.2, Clipper 5.3 that have been patched.
Does not apply to unpatched Clipper, if you are using one of the "time slice stealers" that allowed them to run on faster processors without crashing.
As I recall it...
Its use is just gross, and is usually replaced with a command like sleep(), blocks of code that only respond to system triggers, or some such, unless you only need quick-and-dirty.
David A. Smith
Does not apply to Clipper 5.2, Clipper 5.3 that have been patched.
Does not apply to unpatched Clipper, if you are using one of the "time slice stealers" that allowed them to run on faster processors without crashing.
As I recall it...
Its use is just gross, and is usually replaced with a command like sleep(), blocks of code that only respond to system triggers, or some such, unless you only need quick-and-dirty.
David A. Smith
0 new messages