Answer:
See Explaination
Explanation:
package testscores;
import java.util.ArrayList;
import java.util.List;
public class TestScores {
public List<Integer> scorearray=new ArrayList<>();
public TestScores(List<Integer> scores) throws InvalidTestScore{
this.scorearray=scores;
for(int i=0;i<scorearray.size();i++){
if(scorearray.get(i)>100 || scorearray.get(i)<0){
throw new InvalidTestScore(this.scorearray.get(i));
}
}
}
public double average(){
int tot=0;
for(int i=0;i<this.scorearray.size();i++){
tot=tot+this.scorearray.get(i);
}
return tot*(1.0)/(this.scorearray.size());
}
class InvalidTestScore extends Exception
{
private double amount;
public InvalidTestScore(int Score)
{
System.out.println("Invalid Score "+Score);
}
}
}
Answer:
The answer is B, E, and F
Explanation:
Answer:
An interpreter is quite different from a complier due to the following statement below:
O. An interpreter translates and executes code line by line, while a compiler translates all code at once so that it is ready to be executed at any time.
Explanation:
For an interpreter, it works in translating and execution of the codes line after another line. In a situation where there is a mistake in the code, the next line would not be able to be executed, but rather display error message. On the other hand, compiler translate all codes at once and execute them as a single work.
<em>During its translation of the codes in compiler, should there be any error, it would not be able to execute despite the fact that, the error might be in the last line of the code.</em>
Answer:
Check the explanation
Explanation:
An integer (int) is of two different bytes and each page has 200 bytes in length. What this means is that each row of array A (100 int) will fits perfectly in a page.
(a) For the initial or first array-initialization loop, one column is processed at a time, so a page fault will be generated at every inner loop iteration, with a total of 100*100=10,000 page faults.
(b) And when it comes to the second array-initialization loop, one row is processed at a time, and a page fault is generated at every outer loop iteration, with a total of 100 page faults.
Hence second array-initialization loop, has better spatial locality.
I believe it is C, I'm so sorry if im incorrect.
