I've read that C ++ is a super-set of C and provides real-time implementation by creating objects. Apart from this, C ++ is locked to the real world because it is rich in object-oriented concepts.
What are the concepts in C, which can not be implemented in C?
- Some say that we can not write methods in C, so how can we get different tastes
printf ()? For exampleprintf ("sachin");will printsachinandprintf ("% d,% s", count, name);print1, sachinis a whole number whose value is 1 and the name is a letter that is initililsed with"sachin". - Some say data is acquired in intangible C ++, so what about structures?
Some respondents here argue that most things that are prepared with C ++ code Can be done, it can also be produced with C with ample ambition. This is true in some parts, but it is impossible to get some things naturally unless you modify the compiler to get out of the standard.
Fake:
- (indicator for parent-structure in hair structure)
- Polymorphism (Function Points
- Data encapsulation Ul (
- (which can also be called preprocessor step 2)
- by logic (try to simulate it with some oval, but never really stops
- (Constructors and destructors are automatically applied in C ++, so your stack resources are handled safely in their scope)
- ( You can cast almost anything in C)
Impossible:
Check-out:
- (a C library)
- I once posted while using C instead of ELLOC
Explanation on RAII:
This concept is usually misinterpreted when its most important aspect - built-in Resource management, i.e. the concept of guarantee (usually at the language level) that resources are properly controlled, some believe that by obtaining RA, this responsibility can be done except for the programmer (eg. Clear Destruction Call on Geto Label), which unfortunately does not come close to providing RAI security principles as a design concept.
> A quote from a Wikipedia article which clarifies this aspect of RAI: "Therefore, resources need to be tied to the life of suitable objects.
No comments:
Post a Comment