Print person1's kids, apply the IncNumKids() function, and print again, outputting text as below. End each line with a newline. Sample output for below program with input 3:
Kids: 3
New baby, kids now: 4

public class PersonInfo {
private int numkids;

public void setNumKids (int setPersonsKids) {
numKids setPersonsKids;
}
public void incNumkids() {
numKids nueKids 1;
}
public int getNumkids () {
return numkids;
}
}
public class CallPersonInfo {
public static void main (String [] args) {
Scanner scnr = new Scanner (System. in);
PersonInfo person1 = new PersonInfo();
int personsKid;
personsKid = scnr. nextInt();
person1.setNumKids (personsKid);
/* Your solution goes here*/

What is the name of the option in most presentation applications with which you can modify slide elements? 1. the option enables you to modify a slide element in most presentation applications.

When making changes to optimize part of a processor, it is often the case that speeding up one type of instruction comes at the cost of slowing down something else. for example, if we put in a complicated fast floating-point unit, that takes space, and something might have to be moved farther away from the middle to accommodate it, adding an extra cycle in delay to reach that unit. the basic amdahl's law equation does not take into account this trade-off. a. if the new fast floating-point unit speeds up floating-point operations by, on average, 2ă—, and floating-point operations take 20% of the original program's execution time, what is the overall speedup (ignoring the penalty to any other instructions)? b. now assume that speeding up the floating-point unit slowed down data cache accesses, resulting in a 1.5ă— slowdown (or 2/3 speedup). data cache accesses consume 10% of the execution time. what is the overall speedup now? c. after implementing the new floating-point operations, what percentage of execution time is spent on floating-point operations? what percentage is spent on data cache accesses?

Worth 50 points answer them bc i am not sure if i am wrong