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.
IMHO, ioctl is not a substitute for Input/Output control.
It is a function call for controlling I/O devices and streams: (from Sun's
docs on their website)
NAME ioctl ? control device
SYNOPSIS #include <unistd.h>
int ioctl(int fildes, int request, /* arg */ ...);
DESCRIPTION The ioctl( ) function performs a variety of control functions on
devices and STREAMS. For non-STREAMS files, the functions performed by this
call are device-specific control functions. The request argument and an
optional third argument with varying type are passed to the file designated
by fildes and are interpreted by the device driver.
What you seem to be up against is the use of ioctl (the call both
generically and in context) in engineering text. It is very common to use a
call name as a verb, adjective, and noun. It isn't obvious to engineers
outside the group that commonly uses the call. If you want to copy-edit the
language, then you need to be very careful to understand the intent of the
language choice. Double-check with the engineer.
Whatever your choices, the use of ioctl as a term is not generic outside of
Sun or Sun-type (unix flavors???) apps/devices.
Hope that helps...
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
Acrobat & FrameMaker Seminars: PDF Best Practices, FrameMaker-to-Acrobat
Advanced Techniques, FM Template Design, Single Sourcing with FrameMaker
in Brussels (Oct), and in Montreal & Dallas (Dec): http://www.microtype.com/1
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.