![]() |
|
[C++] Understanding Pointers and Their Useage - Printable Version +- Sinisterly (https://sinister.ly) +-- Forum: Coding (https://sinister.ly/Forum-Coding) +--- Forum: C, C++, & Obj-C (https://sinister.ly/Forum-C-C-Obj-C) +--- Thread: [C++] Understanding Pointers and Their Useage (/Thread-C-Understanding-Pointers-and-Their-Useage) Pages:
1
2
|
RE: [C++] Understanding Pointers and Their Useage - invisal - 03-14-2014 (03-14-2014, 03:14 AM)TheUninvited Wrote: @invisal I think using compiler as an argument is irrelevant. We only interest in semantics of the language and the final output from compiler. Something in between is irrelevant. Now, it is hard to argue whether all variable are objects including primitive type because there is no clear definition of "Object". In the object-oriented programming paradigm, "Object" refers to the instance of the class. In this case, no, pointer variable is not an object. It may point to the object. Language syntax should be independent of parsing technique. Parsing technique is enforced by language specification not vise versa. For example: 1 + 7 = 8. In whatever parsing technique you use, you need to ensure that the final result meets the specification. RE: [C++] Understanding Pointers and Their Useage - ArkPhaze - 03-14-2014 Actually, object is subjective with many languages, so I would also agree with what invisal is saying. An object can refer to System.Object which everything inherently, either directly or indirectly, implements in some form or another. In C++ object typically refers to an instantiated class, since it's an geared to the constructs and structure of the OO paradigm. Plus if you've ever decompiled anything with an advanced tool like IDA pro, you'll know that all you have left is references to memory addresses to where functions reside, even though for debugging purposes, you can rename those within the workspace to suit your own readability needs. |