Thanks Mark. Assembly would be quite intensive, but standard C is not an Object Oriented Programming language neither - and there are others as well.
The thing about OOP is that Class and Class Inheritance isn’t always obvious where “collateral impact” is concerned and although OOP does streamline program implementation I wonder if it doesn’t afford introduction of some of these issues. I cannot see a realistic possibility of Apple changing to a non-OOP coding language, but I think this does help explain why these issues arise after a system upgrade. I just cannot entertain the notion that Apple - nor any company - engineers would intentionally or carelessly introduce some of these issues. Correcting such problems is so very expensive! **************** - Bill from Ino, Wisconsin - "Always acknowledge a fault. This will throw those in authority off their guard and give you an opportunity to commit more." - US Humorist, Mark Twain (1835 - 1910) -- The following information is important for all members of the V iPhone list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/viphone@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "VIPhone" group. To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscr...@googlegroups.com. To post to this group, send email to viphone@googlegroups.com. Visit this group at https://groups.google.com/group/viphone. For more options, visit https://groups.google.com/d/optout.
