There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Holden Hodgdon wrote:ok, so what I'm understanding is that you establish either public or private class "entities" outside of where the actual code is run. from there you can then use those established "classes" to dynamically generate instanced variables based on the root classes, that way you don't have to hard code in multiple copies of the same thing.
Jesper de Jong wrote: ...
define and use a class for the student record. the class should have instance variables for the quizzes, mid term, final, over all numeric score for the course, and final letter grade. the over all numeric score is a number in the range of 0 to 100 which represents the weighted average of the student's work. this class should have methods to compute the over all numeric grade that set the appropriate instance variables. your class should have a reasonable set of accessor and mutator methods, an equals method, and a toString method, whether or not your program uses them. you may add other methods if you wish.
define and use a class for the student record. the class should have instance variables for the quizzes, mid term, final, over all numeric score for the course, and final letter grade. the over all numeric score is a number in the range of 0 to 100 which represents the weighted average of the student's work. this class should have methods to compute the over all numeric grade that set the appropriate instance variables. your class should have a reasonable set of accessor and mutator methods, an equals method, and a toString method, whether or not your program uses them. you may add other methods if you wish.
define and use a class for the student record.
the class should have instance variables for the quizzes, mid term, final, over all numeric score for the course, and final letter grade.
the over all numeric score is a number in the range of 0 to 100 which represents the weighted average of the student's work.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors