When I started in 1980, we used 'objects' by copying the last similar program 😀from someone else 's library.
Sent from Proton Mail mobile -------- Original Message -------- On May 29, 2023, 9:47 AM, Andrew Rowley wrote: > On 29/05/2023 8:40 am, Tom Ross wrote: > ... The real > worl is not object > oriented...we do no instantiate a customer object and then > invoke a > 'send_a_bill' method on that object. We procedurally decide that it > is time > to send a cusotmer a bill and do it! I'm not sure I would agree... it > probably depends on what sort of code you work with, but I think it would be > extremely common to have a customer object and to have a bill object. Then > e.g. you might have dozens of ways line items might be added to a bill, but > the bill checks its status when you try to add an item and won't allow it if > the bill has already been sent. A program always has a sequence of actions > i.e. a procedure, but with well designed object classes you don't need to > know the procedures beforehand. > Re-usable tested mehods that could be > re-used to build > applications it just not really happening! It's happening > a lot! -- Andrew Rowley Black Hill Software > ---------------------------------------------------------------------- For > IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
