- Home
- Member
- AXT
- AXT's entries
- Duplicate Inheritance from base classes is prohibited.
Duplicate Inheritance from base classes is prohibited.
- 141
- 2
- 2
This journal is about my work related 'programming'.
I took a code review of our source code by my customers today.
(I mean I was reviewee(Is this proper English?) and they were reviewer.)
They told me that DON'T USE DUPLICATE INHERITANCE FROM THEIR BASE CLASSES.
(Naturally Single Inheritance is OK.)
(Their architecture section offered base classes. They are business section.)
I don't know why they told such strange things.
I think inheritance is best way of object oriented programming.
However it's difficult to learn it, then code beginners aren't able to understand them.
Mm, I think they would try to change our source code after I deliver to it.
Therefor it must be better easier than complicate.
Not using inheritance properly maybe increase the cost of all kind of test.
My boss and I made and handed to our customer the report of reason document of delaying schedule, which it causes that to change code and retest the module already tested.
We'll become what we become.
Thank you for your reading.
I took a code review of our source code by my customers today.
(I mean I was reviewee(Is this proper English?) and they were reviewer.)
They told me that DON'T USE DUPLICATE INHERITANCE FROM THEIR BASE CLASSES.
(Naturally Single Inheritance is OK.)
(Their architecture section offered base classes. They are business section.)
I don't know why they told such strange things.
I think inheritance is best way of object oriented programming.
However it's difficult to learn it, then code beginners aren't able to understand them.
Mm, I think they would try to change our source code after I deliver to it.
Therefor it must be better easier than complicate.
Not using inheritance properly maybe increase the cost of all kind of test.
My boss and I made and handed to our customer the report of reason document of delaying schedule, which it causes that to change code and retest the module already tested.
We'll become what we become.
Thank you for your reading.
Latest entries
| Lang-8 published to share a journal to the Facebook. (4) |
| Starting Cool Biz (5) |
| Facebook is funny place (7) |
| Good Button I misunderstood (6) |
| Sunshine Aquarium (4) |
Entries by Month
Multiple Inheritance from base classes is prohibited.
I attended a code review of our source code by my customers today.
(I mean I was reviewee(Is this proper English?) and they were reviewer.)
Yes that's fine
They told me NOT TO USE MULTIPLE INHERITANCE FROM THEIR BASE CLASSES. (or, "told me that I shouldn't use")
(Their architecture division provided the base classes.
"division" or "department" is more likely than "section" with companies.
They are from the business division.)
I don't know why they said such strange things.
"to tell" is not usually used without an indirect object (the person who is being told). So if you said "why they told me such strange things", that would be OK, but "why they told such strange things" is not OK, or at least it makes it sounds as though you are trying to be poetic :).
I think inheritance is the best way to do object oriented programming. (or perhaps you mean "the best feature of object oriented programming")
However it's difficult to learn it, so beginning coders aren't able to understand it. (or "novice coders")
Mm, I think they will try to change our source code after I deliver to it.
Therefor it must be better easier than complicated.
Not using inheritance properly maybe increases the cost of all kinds of test.
My boss and I drew up (or produced) and handed to our customer the report giving the reasons for delaying the schedule. The reasons were changes to the code and the need to retest the module which we had already tested.
We'll see what happens.
I think that's waht you mean!
Thank you for your reading.
Your explanation is very kind.
or "We'll see what we shall see" (a set expression)