TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: on the fly From:Maynard Hogg <maynard -at- GOL -dot- COM> Date:Wed, 14 May 1997 09:07:35 +0900
At [Mon, 12 May 1997 15:37:30 -0400]
Phillip Wilkerson <phillipw -at- allensysgroup -dot- com> wrote:
> I guess "on the fly" would be termed a colloquialism (i.e., too
> technical writing); however, it has been used so much in the computer
> that it is tantamount to computer jargon (i.e., too esoteric for technical
> writing). In either case, Arlen is right: better to use common words to
> communicate the idea.
Note that Java virtual machine implementations (in MSIE and Netscape, for
use "just in time" compilers that compile Java bytecodes into native
machine language "on the fly". I don't know why Sun and followers went
with Toyota's term instead of the latter.
It didn't take me long to remember the Japanese translation for the term
in a programming context: sono tsudo, a term used in regular speech to
mean things like "each time" or that old buzzword "on demand".
In my limited programming experience, "on the fly" refers to things like
pick lists and other dialog box components that are built as needed and
then *thrown away* as soon as the user closes the dialog box. (There are
programs that build dialog boxes on the fly, but that is probably A Bad
Thing from the internationalization viewpoint, if only because of the
way that string lengths change.) It is this temporariness that makes me
suspicious of Peter Brown's <pbrown -at- mks -dot- com> "on-the-fly updating".
(That doesn't stop me from using his company's products, however. <g>)
Perhaps this is an example of the type of overuse warned by Susan W.
Gallagher <sgallagher -at- EXPERSOFT -dot- COM> and Phillip Wilkerson
<phillipw -at- allensysgroup -dot- com>.