All the posts and topics that contain only an error report will be moved here after the error is corrected. This is to ensure that when users view a question in ETS Viewer, the "Discuss" button will not indicate the presence of a discussion that adds no value to the question.
The 5h and 6th options are given as the correct answers:
- Implement compute() method in RecursiveAction that computes the new value but does not return anything.
- Create a RecursiveAction that subdivides the task into two, then forks one of the tasks and computes another.
Now why is the 4th option not a correct answer as well? It's the same thing.
- Subclass RecursiveAction and implement the compute() method that computes the new value but does not return anything.
I see that option 4 and 6 are given as correct answer. Option 5 is wrong and the explanation to that option says: RecursiveAction is not an interface. It is an abstract class.
So, which one is the correct answer? Someone please kindly confirms. Do I have the right question bank and the right answer?
In the last answer choice,
Create a RecursiveAction that subdivides the task into two, then forks one of the tasks and computes another.
A RecursiveAction does not fork one of the tasks and computes another. That's what RecursiveTask does. Am I wrong? At least, it's inconsistent with the explanation underneath.
1. You can check whether you have the latest version by using Tools->Check for question bank update menu. From the screen shot that you've posted, you seem to have the right version, as is indicated by the messages posted above. Can you please tell me which message caused the confusion so that I can remove it?
2. Option 6 asks you to create a RecursiveAction that subdivides the task into two, then forks one of the tasks and computes another. A sample code is also given that shows you how to do it. Did you go through it?
I am not sure where you got the idea that RecursiveAction does not fork one of the tasks and computes another while RecursiveTask does. Please go through the sample code.
Thank you. I shouldn't have written that. I did not do enough research on my own before I wrote my earlier comment. My apology. After reading up more on this, you are absolutely right and I was wrong.
Schmichael
PS
Is this just on my browser or is anyone seeing everything typed being displayed on just one line after the "Submit" is clicked, i.e. text display not wrapping to the next line after "Submit" is clicked?