Oliver_FF
New Member
- Joined
- Oct 15, 2006
- Messages
- 544 (0.08/day)
Processor | Intel q9400 @ stock |
---|---|
Motherboard | Lanparty P45-T2RS |
Cooling | Zalman CNPS-9500 |
Memory | 8GB OCZ PC2-6400 |
Video Card(s) | BFG Nvidia GTX285 OC |
Storage | 1TB, 500GB, 500GB |
Display(s) | 20" Samsung T200HD |
Case | Antec Mini P180 |
Audio Device(s) | Sound Blaster X-Fi Elite Pro |
Power Supply | 700w Hiper |
Software | Ubuntu x64 virtualising Vista |
Cool, thats not a bad effort 
Nit picking though:
q1 - with an inheritance hierarchy you're getting the data members down to the subclasses, but the functions can also be passed down. For instance Staff and Faculty share the same functions showEmployee() and setEmployee(), you can get rid of those and simply make the declarations in Staff protected?
q2 - I had the impression that setInterestRate() should take the value you want to change it to as a parameter, not get it from the command line?
But yeah, looking good

Nit picking though:
q1 - with an inheritance hierarchy you're getting the data members down to the subclasses, but the functions can also be passed down. For instance Staff and Faculty share the same functions showEmployee() and setEmployee(), you can get rid of those and simply make the declarations in Staff protected?
q2 - I had the impression that setInterestRate() should take the value you want to change it to as a parameter, not get it from the command line?
But yeah, looking good
