|
Re: How to: Teach java?
This thought just popped into my head.
Depending on how you organize your code, you probably can almost entirely avoid using Java's OO features, and can simply use it to write the same sort of main (probably multi-threaded) routine, plus data and subroutines, that you would write using Fortran or C.
I'm not advocating doing that, I'm just pointing out that it is a legitimate option that might simplify producing a robot for first-time Java users.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|