Re: [phix] Ambiguity of 'object'

new topic     » goto parent     » topic index » view thread      » older message » newer message
_tom said...

In OOP, actions are associated, and limited to a specific class. That makes learning OOP more difficult. That is why they talk about ''methods'' instead of function|procedure.

This difficulty in explaination is why i said what i did, the way i did, about class and include as. And Irv helped.

Start with a cow.e file, this is the "object", it has variables and procedures.  
It shares some of them. 
 
Copy cow.e, append "cow1" to all the names of whatever is shared in that copy,  
and append "cow1" to the filename. 
 
##Include cow.cow1.e as cow_1## 
Repeat for all cows. Stop when you realise the computer cannot hold enough ram. Class reuses the code of cow.e, but otherwise seems to function the same. Easy to understand? Yes, but no, because then the keyword "method" was introduced!

Geese, i hope i got that right!

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu