Sign in to follow this  
lXciD

Unity Casting void pointers

Recommended Posts

Hi all, I am doing a lot of reading on casting on pointers and are confuse. So I thought I come here to get some views from the community. In my post here, I will not touch on reinterpreted and const cast, just the C cast, static cast and dynamic cast. From my understanding, casting on pointers will make compiler change its view on the type the data is holding. So for example if I use C cast to cast object of class A to an unrelated class B. It will succeed and think the object is now class B even though its illegal from our perspective. (I understand this is reinterpreted cast in C++ but lets just focus on C cast) As for related classes, Casting between a base class to a derived class is more of adding and subtracting pointers. First of all, I read that casting only return 0 if you are using dynamic cast because of the RTTI. Other than that the application have no idea whether a casting succeed or fails on run time. This make me wonder, if you are not using RTTI and dynamic casting, why bother checking for null pointer after a cast? for example...
DerivedClass * d = ( DerivedClass * ) b;
// DerivedClass * d = static_cast<DerivedClass *>( b );
if ( d != NULL )
// if ( d )
{
}
So I conclude that its useless to check for null pointer to determine if a casting succeed or fail. But its a good practice so that if you ever enable RTTI and dynamic cast, your code will become safer. Secondly about void pointer. Casting void pointer essentially falls under the category casting between unrelated pointers. For the following operation:
DerivedClass * derviedObject = new DerivedClass(); // Derived from BaseClass

void * userData = ( void * ) derivedObject;
// void * userData = static_cast<void *>( derivedObject );

BaseClass * baseObject = ( BaseClass * ) userData; // baseObject pointing wrongly
If I were to cast from a derivedObject to a void pointer and then cast the void pointer to a baseObject (a BaseClass pointer), access violation will occurs on baseObject due to there's no adding and subtracting operation occurring on the pointer in question happening during the casting operation (this operation is required for casting between related pointer) as all the operation is treated as unrelated pointers. In order for the following codes to work, I need to store the base pointer in the void pointer and cast it back to base pointer.
DerivedClass * derviedObject = new DerivedClass(); // Derived from BaseClass

void * userData = ( void * ) ( BaseClass *) derivedObject;
// void * userData = static_cast<void *>( static_cast<BaseClass *>( derivedObject ) );

BaseClass * baseObject = ( BaseClass * ) userData; // work
// BaseClass * baseObject = static_cast<BaseClass *>( userData ); // work

DerivedClass * derivedObject2 = ( DerivedClass * ) baseObject; // work
// DerivedClass * derivedObject2 = static_cast<DerivedClass *>( baseObject ); // work

DerivedClass * derivedObject3 = ( DerivedClass * ) userData; // don't work
// DerivedClass * derivedObject3 = static_cast<DerivedClass *>( userData ); // don't work
Of course, this mean that direct casting of userData to DerivedClass pointer will fail too. Would like to ask if I got the right interpretation? :) Please correct me if I'm wrong. Sorry for my poor english. Reference: http://www.codeproject.com/KB/cpp/static_cast.aspx Edit: One more question. If RTTI is enabled. Will casting a void pointer storing a base pointer to its derived pointer and vice versa work?

Share this post


Link to post
Share on other sites
Quote:
Original post by lXciD
if you are not using RTTI and dynamic casting

dynamic_cast is impossible without RTTI.

Quote:
Original post by lXciD
Will casting a void pointer storing a base pointer to its derived pointer and vice versa work?

You mean something like Base* -> void* -> Derived* ?

It will certainly blow up with multiple inheritance. With single inheritance, you may get the desired results on your platform, but I think the behavior is technically undefined. I may be wrong, but I seem to remember that the only safe conversion is

myclass* -> void* -> myclass*

i.e. you have to cast back to the exact same type as before.

Share this post


Link to post
Share on other sites
Quote:
So I conclude that its useless to check for null pointer to determine if a casting succeed or fail.

I conclude that you need to read the standard with respects to dynamic cast, DevFred is correct it requires RTTI and a polymorphic type. There is another use for dynamic cast when you cast to a void pointer it returns a pointer to the most derived class.

Quote:
If I were to cast from a derivedObject to a void pointer and then cast the void pointer to a baseObject (a BaseClass pointer), access violation will occurs on baseObject

Casting from A to void to B is undefined, unless B is of type char( or a variant) or you know enough about your compiler because it could be implementation specific. Also casting to a void pointer is implicit and there is not need for static_cast in your example.

Quote:
... access violation will occurs on baseObject due to there's no adding and subtracting operation occurring on the pointer in question happening during the casting operation (this operation is required for casting between related pointer) ...

You are talking about implementation specific behaviour here.

Quote:
One more question. If RTTI is enabled. Will casting a void pointer storing a base pointer to its derived pointer and vice versa work?

Implementation defined, a void pointer has no type information.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628333
    • Total Posts
      2982126
  • Similar Content

    • By BAG Labs
      Mobile SoS

      Platform: Android
      Genre: Board
      Link: Google Play
       
      This games sharpen memory and test your strategies to place S-O-S pattern within time limit and serve 3 difficulties as Easy, Normal, and Hard.

      Goals of the game is to put S-O-S words in patterns (Horizontal, Vertical, and Diagonal) alternately with enemy.
       
      Features:
      Single Player Multiplayer Achievements Leaderboards  
       
      Screenshot:

       

       

       
      Link: Google Play
       
      Please help us improve this game with review
    • By abarnes
      Hello!
      I am a game development student in my second year of a three year program and I would like to start building my portfolio. I was thinking of creating some games to show what I can do to potential employers since I wont have any work related experience when I graduate. But as I'm sure you all know there are tons of ways to approach developing/designing a game and I'm curious if anyone had any insight as to any "standards" that come with this? Is it okay to use game engines like Unity, Unreal, Game Maker etc? Or would it be better to make a game from scratch to better show case your skills? Any and all advice will be greatly appreciated!
    • By Hilster
      Hello 2D Artists,
      I've started making a 2D Puzzle Adventure game for mobile and I'm looking for someone who would want in on creating assets for the game. The core of the programming is pretty much complete, you can walk within the grid laid out and push boxes, when there is an object on top of a pressure pad it will activate the linked objects or if there is one object with multiple linked pressure pads it requires you to activate all points for the object to become active. 

      The level iteration for the game is quick and simple, a Photoshop file that is made of individual pixels that represents objects is put into the game and it creates the level out of those pixels with the assigned objects.
      The objects that need sprites created so far is the character, box, pressure pad, door, trap door, the walls, the stairs and the tiled background.
      I intend to add more objects so the amount I'd like to add will be extended.
      My motivations for posting here is to have something that looks nice to be able to display on my portfolio, so if you're looking for a working game that you can place your art into and improve the look of your portfolio then we're in business.
      Please reply with a few past examples of your art below and I'll be in touch!
    • By thefollower
      Hi
      I have set up my TcpClient to connect to my server and that works fine. But i am a bit confused how i read messages from the network stream with it continuously running via async, without ever closing the connection ?
      My TcpClient Manager class has:
       
      public async Task<bool> Connect(string address, int port) { try { await _tcpClient.ConnectAsync(address, port); IsConnected = true; return true; } catch(Exception e) { Debug.Log(e); return false; } } public async Task<int> Read(byte[] readBuffer) { if (!IsConnected) return -1; using (var networkStream = _tcpClient.GetStream()) { try { var bytesRead = await networkStream.ReadAsync(readBuffer, 0, readBuffer.Length); return bytesRead; } catch (Exception e) { Debug.Log(e); IsConnected = false; return -1; } } }  
      So i thought to just run a co-routine and call Read constantly to get the most recent message, but that doesn't make much sense to me since a co-routine would be blocked with the await. How is this actually done? The MS Docs don't have very good Async examples with the TcpClient class so i don't know fully get how to keep calling Read correctly.
  • Popular Now