English Language & Usage Asked by Terry Li on February 8, 2021
I’m reading about the C++ Boost library, and the following sentence from Boost.ORG drew my attention:
Once the two steps have been successfully completed, the process can
start writing to and reading from the address space to send to and
receive data from other processes. Now, let’s see how can we do this
using Boost.Interprocess.
I assume the sentence in bold should be written as let’s see how we can do this.
Has the original sentence been mistakenly written by somehow (like perhaps by a non-native speaker, for example), or was this reversed order intended to emphasize something?
The sentence should be written as
Now, let's see how we can do this.
Alternatively you can write
Now, let's see. How can we do this?
Answered by user2683 on February 8, 2021
You are right. The correct sentence would be
Now let's see how we can do this.
The incorrect form you've read demonstrates a fairly common English mistake among non-native speakers, especially those whose native language allows for omission of the subject pronoun (such as the Romance languages).
The confusion arises from three points:
In some languages, the subject pronoun "we" would not be used explicitly in either the question or statement form. Example (Spanish, no special characters):
..donde podemos encontrar el perro... ("where we can find the dog")
¿Donde podemos encontrar el perro? ("Where can we find the dog?")
where the only difference is that one is written as a question.
Answered by yoozer8 on February 8, 2021
Your intuition is correct; the sentence should be:
Now, let's see how we can do this.
I share your suspicion that the page in question was written by a non-native speaker. In my experience, non-natives have a very hard time distinguishing between the grammar of questions, which trigger inversion, and relative clauses, which do not trigger inversion. The difficulty is that both types of clauses are headed by the same words (who, what, where, when, why, how), and it's easy for non-natives to develop the incorrect habit of always inverting following these words.
Answered by JSBձոգչ on February 8, 2021
Embedded questions normally don't allow Subject-Auxiliary inversion, though it's required for normal questions:
However, in spoken English (which is similar to the chatty, informal style used in many computer books), an embedded question complement can optionally invert the subject and the first auxiliary verb, like a regular question does.
There's a pragmatic distinction between the two forms, with and without the inversion. The presenting construction -- the one that resembles a real question -- is in fact intended to operate like a real question, and thus invite an answer from the addressee, rather than being intended to be interpreted as a simple rhetorical question.
For that reason, it's often encountered punctuated like a question; and sometimes a comma intonation -- or even a semicolon -- dashes in to separate the clauses.
Now, this particular instance is in a piece of writing, where any question the author asks has to be rhetorical, after all, so this usage in this context probably is meant simply to increase the chumminess of the Boost.Interprocess salesman's pitch. If you're interested, there's an extensive literature on such syntactic marking in Pragmatics; the key term is "indirect question".
Executive Summary:
Answered by John Lawler on February 8, 2021
This is only a problem if we leave out the start of the phrase and concentrate on trying to interpret 'how we can do this' as opposed to 'how can we do this' by themselves,'how we can do this' by itself being clearly wrong in English.
However, that's not the point. I suggest that 'Let’s see how can we do this' isn't at all ungrammatical; it's simply wrongly punctuated.
Among several other possibilities, change that to 'Let’s see: "How can we do this?"' and what problem remains, please?
Answered by Robbie Goodwin on February 8, 2021
Get help from others!
Recent Questions
Recent Answers
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP