Tim, *programming* in the real world. The problems that you initially described employ algorithms (ie mechanical, repeatable, defined procedures) that would all be similar in pretty much any programming language.
And no, they are not typical of 'real-world' problems. A real-world problem is much more complex (and sometimes less defined); such a problem as below is just a small part of the puzzle, you might be required to solve several such problems *per day* in the course of solving the much bigger problem at hand. The problem might be, 'total (nett) all the specified equity orders into the user's local currency. each order may have different fee structures and different taxation and these may possibly be in different currencies to the order total. the forex transaction will be executed at a later time (on completion of the orders) based on a forex rate obtained now and guaranteed for 24 hrs. if the rate is older than 24 hrs, expire the forex transaction and start again.' I'm sure if I showed you that code your head would explode. Mine would have, just last week, before my team & I wrote the actual code. The code is *wrong* place to start. As has been said, the ability to decompose such problems into smaller parts is very critical, as is the ability to make those parts work to the solution as a whole. This is entirely independant of the programming language, indeed it is true even if we were using a pencil and paper. regs scot. > IS this the sort of code you deal with in the real world ? > > If so, then my deepest fears really are true -- that java in the > real world > may be a little too difficult for me to handle. ______________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
