Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #203271
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: About /dev/sr impatience with automatic tray loading |
| Date | 2018-12-11 15:50 +0100 |
| Message-ID | <x3Rwd-Y3-7@gated-at.bofh.it> (permalink) |
| References | <x3yWC-6pO-13@gated-at.bofh.it> <x3A2m-7gZ-3@gated-at.bofh.it> <x3Pup-8d9-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
mick crane wrote: > On 2018-12-10 20:02, Thomas Schmitt wrote: > > For the purpose of sr_drive_status(), the loop is really inappropriate. > > This function shall obtain the drive status and not wait until the > > status of the medium is decided. > > > completely off the topic but I have noticed that people whose first language > might not be english use > "shall" as apposed to "will" or "should". It seems a little bit old > fashioned but maybe it isn't. The English use it more than Americans do. "Shall" has a connotation of ordering future action. Americans nearly always prefer "should". "Will" is a prediction of future action. "Should" is a desire for future action, with an acknowledgment that it might not go that way. In a question, it asks for advice on desirability. "May" is a speculation on future action, with less certainty and less imputed desire. In a question it asks for permission. "Can" is a description of a possible future action, and sometimes carries the connotation that the action is appropriate. Americans like to use this instead of "may", but they generally know that "may" is permission and "can" is capability. "Might" is either used to request permission or to describe a low-probability future action. Americans rarely use this this in question form. -dsr- (American/British hybrid)
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
About /dev/sr impatience with automatic tray loading "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 15:00 +0100
Re: About /dev/sr impatience with automatic tray loading Gene Heskett <gheskett@shentel.net> - 2018-12-10 16:00 +0100
Re: About /dev/sr impatience with automatic tray loading "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 18:50 +0100
Re: About /dev/sr impatience with automatic tray loading Gene Heskett <gheskett@shentel.net> - 2018-12-10 20:00 +0100
Re: About /dev/sr impatience with automatic tray loading "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-10 21:10 +0100
Re: About /dev/sr impatience with automatic tray loading Gene Heskett <gheskett@shentel.net> - 2018-12-11 01:20 +0100
Re: About /dev/sr impatience with automatic tray loading "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-11 12:40 +0100
Re: About /dev/sr impatience with automatic tray loading Gene Heskett <gheskett@shentel.net> - 2018-12-11 18:00 +0100
Re: About /dev/sr impatience with automatic tray loading "Thomas Schmitt" <scdbackup@gmx.net> - 2018-12-11 18:30 +0100
Re: About /dev/sr impatience with automatic tray loading Greg Wooledge <wooledg@eeg.ccf.org> - 2018-12-11 18:40 +0100
Re: About /dev/sr impatience with automatic tray loading Tony van der Hoff <lists@vanderhoff.org> - 2018-12-11 18:50 +0100
Re: About /dev/sr impatience with automatic tray loading John Hasler <jhasler@newsguy.com> - 2018-12-11 20:50 +0100
Re: About /dev/sr impatience with automatic tray loading Gene Heskett <gheskett@shentel.net> - 2018-12-11 20:30 +0100
Re: About /dev/sr impatience with automatic tray loading mick crane <mick.crane@gmail.com> - 2018-12-11 13:40 +0100
Re: About /dev/sr impatience with automatic tray loading Dan Ritter <dsr@randomstring.org> - 2018-12-11 15:50 +0100
Re: About /dev/sr impatience with automatic tray loading Erik Christiansen <dvalin@internode.on.net> - 2018-12-12 01:10 +0100
Re: About /dev/sr impatience with automatic tray loading Dan Ritter <dsr@randomstring.org> - 2018-12-12 12:30 +0100
Re: About /dev/sr impatience with automatic tray loading David Wright <deblis@lionunicorn.co.uk> - 2018-12-12 21:20 +0100
csiph-web