Content deleted Content added
"Real-world objects" |
typo "to to" (fixed to eliminate "noise" in typo searches) |
||
Line 13:
:About subprogram. That is exactly my point. There are a lot of concepts related to subroutine, function, procedure and methods. But we don't want to have a separate article for each one. What I am trying to do here is the same thing. Because for programmers, the difference is a huge matter, but for general audience, they want to know more about what is happening in cs. We don't want to teach them OOP should be bah bah bah. That is a difference seen in articles of wikipedia and textbooks. Because most of textbooks or websites have a POV such as OOP should be. Yeah, I can start certainly I can start an article called object theory but the trouble is we need to make sure history is combined. What about renaming this first, add more about object-based OOP and difference between class-based and object-based and then decide what name should be given or without renaming, start adding such point. This is just a chiken and egg problem. I don't care which one is first. -- [[User:TakuyaMurata|Taku]] 16:17 23 May 2003 (UTC)
But why choose a word that no-one uses. That makes no sense whatsoever. I wouldn't expect to find an article about [[fishing]] under [[fish hunting]]. To the best of my knowledge, few people if any use the word subprogram to mean a subroutine or procedure. Subroutine is a word that assembler programmers generally use and it makes no assumption about whether there is a return value of side effect, or whether it is a member of a class or not. It just means a group of instructions that you jump
I am against the idea of moving this page, because by adding stuff about other systems with objects or if you like widgets that do not embody OO principles you are diluting it and moving away from OOP. [[User:Mintguy|Mintguy]] 16:30 23 May 2003 (UTC)
| |||