Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I understand that in object-oriented programming, an object is an instance of a class. If it's an instance, I misunderstand why does it need the term object at all (we could just say "instance"). ...
#4: Nominated for promotion
by
Alexei
·
2022-02-13T11:36:20Z (almost 3 years ago)
#3: Post edited
by
hkotsubo
·
2022-01-28T12:26:58Z (almost 3 years ago)
minor fixes
Why object-oriented instead class-oriented?
- Why object-oriented instead of class-oriented?
I understand that in object oriented programming, an object is an instance of a class.If **it's** an instance, I misunderstand why do need the term object at all (we could just say "instance").Wouldn't it be more practical to say that this programming is class-oriented and that classes can be instantiated or not?
- I understand that in object-oriented programming, an object is an instance of a class.
- If **it's** an instance, I misunderstand why does it need the term object at all (we could just say "instance").
- Wouldn't it be more practical to say that this programming paradigm is class-oriented and that classes can be instantiated or not?
#2: Post edited
- I understand that in object oriented programming, an object is an instance of a class.
If **it's** the instance (of a class), I misunderstand why do need the term object at all (we could just say "instance").- Wouldn't it be more practical to say that this programming is class-oriented and that classes can be instantiated or not?
- I understand that in object oriented programming, an object is an instance of a class.
- If **it's** an instance, I misunderstand why do need the term object at all (we could just say "instance").
- Wouldn't it be more practical to say that this programming is class-oriented and that classes can be instantiated or not?
#1: Initial revision
Why object-oriented instead class-oriented?
I understand that in object oriented programming, an object is an instance of a class. If **it's** the instance (of a class), I misunderstand why do need the term object at all (we could just say "instance"). Wouldn't it be more practical to say that this programming is class-oriented and that classes can be instantiated or not?