Printable View
Well thats not much difficult, me and my mates tried that alot of time and we did get professor(s) changed easily, just that me and my mates get graduated one semester late :sick:Quote:
Originally Posted by cilu
To OP:
If you don't want to get graduated one semester late, then its better to get yourself adjusted with some other class with better profesoor. Thats what experience tells me :(
Where are iterations of structures created and where are iterations of a class created? (Heap/stack)? What about in Managed C++?
Is this a difference as well?
Brad!
They're the same for class and struct.Quote:
Originally Posted by Brad Jones
If you declare a fully concrete type, it doesn't matter if it's struct or class, it will be on the stack.
If you create a dynamic type, then it's placed on the heap.
Whether it's a class or struct is not relevant as to whether it's put on the stack or heap.
Digressing a bit from the forum topic, but staying on topic with the thread....
I asked the questions simply so I could point out that in C#, things are a little different....
In C# structs and classes differ in that structs are considered value types rather than reference types. Classes are reference types.
Brad!
Perhaps more that a "little" different. Well, if you want to point the differences between structs and classes in C#, then there are more:Quote:
Originally Posted by Brad Jones
- classes support inheritance, but structs which are derived from object are implicitly sealed
- a class can have a destructor, a struct cannot
- a class can define custom parameterless constructor and initialize instance fields, but a struct can't; if a struct declares a constructor all fields must be assign in the constructor
So the structs in C# are quite different from the ones in C++.
Minor quibble:Quote:
Originally Posted by Paul McKenzie
classes inherit privately by default, structs inherit publically. Subtle difference.
Good point.Quote:
Minor quibble:
classes inherit privately by default, structs inherit publically. Subtle difference.
Here Base, which is a structure, is inherited privately by default... but that doesn't matter, because it's a class that inherits it... :wave:Code:struct Base {};
class Derived : Base {};
Yes, I should have stated that much better than I initially did.Quote:
Originally Posted by Graham
Regards,
Paul McKenzie
AWESOME thread guys, I love the replies here. I'm glad I have all of these imaginary differences cleared up :)
Thanks for all the help guys! A+!
**EDIT**
I got the SITE MANAGER to post to my thread!!! :eek: SWEET!
Oh one more thought...
Can structures use polymorphism and abstraction?
Yes.Quote:
Originally Posted by MrDoomMaster
class and struct are the same excpeted for the default public VS default private issue.
So since a class can use polymorphism/abstraction, then a struct can do the same.
lol another thought....
I don't mean to defy anything you guys have said, because I'm most certain you know what you're talking about... I am just curious, how are you able to determine the internal workings of classes and structures? How can you PROVE that classes access their data exactly as structures do?
The only thing I can think of is looking at the disassembly code.
Any comments?
Assembly code has nothing to do with it as it is compiler specific. The standard notes no differences between the types (that we haven't already discussed).
As HeartBreakKid says: we know because the Standard says so. Compilers, assembly, architecture, apple pie... all irrelevant.Quote:
Originally Posted by MrDoomMaster
Oh okay... So the standard says that they are both the same internally and externally?
Internal being the very raw machine code of them both,
External being the way we code them in the IDE.