Skip to main content

Differences between ways to express future actions


I asked this question on a different site but I haven't gotten a useful answer. Could you tell me the difference in meaning between these sentences?




  1. Do you think you will visit them next week?

  2. Will you visit them next week?

  3. Are you going to visit them next week?

  4. Are you visiting them next week?

  5. Are you going to be visiting them next week?

  6. Are you planning to be visiting them next week?

  7. Do you plan to visit them next week?



Will there be any difference in the answers?




  1. I think I will visit them next week.

  2. I will visit them next week.

  3. I am going to visit them next week.

  4. I am visiting them next week.

  5. I am going to be visiting them next week.

  6. I am planning to be visiting them next week.

  7. I plan to visit them next week.



Can I use "planning to" instead of "going to"? (E.g. "Are you planning to visit them next week? — Yes, I am planning to visit them next week.") Which of these sentences show that the subject of conversation has already been discussed? For example, I talked with a friend of mine about my plans to visit somebody. So my friend is aware of my plans.


And my last question. Which of these seven sentences express that the action will certainly take place?




Comments

Post a Comment

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...
Post a Comment
Read more

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...
Post a Comment
Read more