From Paul Walker · 1996-04-09 03:19 · #69263 in DRIVING
In reply to VB/TBV/VBC++ (was Cop by Lee Borgea
Hi Pat, On 06 Apr 96 00:03:00, Pat Winstanley was talking to Paul Walker about Re: VB/TBV/VBC++ (was Cop... PWi> @MSGID: 2:250/107.99@fidonet 3165feb5 Strange MSGID. Actually, anyone know how these MSGID's are calculated?! PWa>> Usually, it's Object Orientated - ie, you can define and use objects ;-) PD>> ye-es...but why's that so good? PWa> Er... right, I'll be off now, see ya... ;) PWi> ROFL! Glad you liked it! :-) PWi> Actually, while your explanation was clear (and correct) as far as it Hey, that makes a change! Usually I lose people by the third sentence... :-) PWi> went, I think there is much more to objects than simply re-usability. PWi> The whole concept seems to imply a completely different way of looking PWi> at things. For sure. I couldn't see what the benefit was until I tried them in this program I mentioned, and then it all becomes clear. I think that's about the only way to see the difference, to be honest - code a program using them. PWi> From what I can gather the power of inheritance seems to be crucial. [snip] PWi> these panels does essentially the same thing - displays a set of PWi> choices, then when a choice is clicked, sends a message out to say PWi> which value has been chosen. That sounds intriguing. The book I learnt it from (or got the basic idea, anyway) didn't do something that complicated. It just had the idea of shapes - you know, triangle, rectangle, etc. You started with a base class, called (I don't know) eg. shape, with some of the methods defined as virtual. (BTW - I know /you/ know what this is, but I'm hoping Peter's still reading) The virtual bit just means that for each object you define from the base class, you have to supply that procedure. So you'd have a different draw routine for each shape, but the move routine would be the same. I must be honest, I never got into this, because I didn't need it. However, the keyboard thing is totally different, because it's got different numbers of buttons on it. How do you do that? (You might want to netmail me... I use Pascal a lot, but've never tried Delphi) PWi> From what I've learned, the idea is to take a basic idea, generalise PWi> it as far as possible, then use that underlying engine to inherit and PWi> adapt from. Real black-box stuff! Or as someone else I heard put it, PWi> "Keep it simple, stupid". :-)) That's a fairly good description. I think the basic idea was to define an object so that you *never* needed to manipulate an attribute directly; and also so that people who used it could do so without knowing *how* a procedure did something, just *what* it did. Same idea as units, I s'pose. Eek - did I really just write all those lines of wibble? Oh dear... _ |_) | aul paul.walker@esoftc.seuk.com <No files> ... Hasta la vista, ...baby! --- Blue Wave v2.12 [NR] * Origin: Highlander BB's - Gloucester [ +44-1452-384702/557 ] (2:253/418)