Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualBlackMoons

Posted 23 August 2013 - 03:29 PM

Oh. I thought that & would still cause a copy when passing from angelscript to C++, when asEP_ALLOW_UNSAFE_REFERENCES was false.

 

Thanks for clearing that up.

 

Is it just when passing to angelscript that & makes a copy of the object if asEP_ALLOW_UNSAFE_REFERENCES is false?


#1BlackMoons

Posted 23 August 2013 - 03:28 PM

Oh. I thought that & would still cause a copy when passing from angelscript to C++, when asEP_ALLOW_UNSAFE_REFERENCES was false.

 

Thanks for clearing that up.


PARTNERS