Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 07 May 2013
Offline Last Active Jun 13 2013 10:55 AM

Posts I've Made

In Topic: Help with Copy Constructor and Object handle as argument

15 May 2013 - 05:03 PM

Andreas, the compile worked ok with my Copy(const image @&in), the runtime went into an loop when executing it. I didn't debug it as I knew I was probably doing something I shouldn't.


I tried the copyconstructor and it works, but as any other reference input it doesn't accept @ tag which maybe makes the syntax confusing or maybe not... there is something about the object handle syntax I am not 100% comfortable. 

In Topic: AngelScript 2.26.3 is out

09 May 2013 - 09:11 PM

Thanks, fantastic work. The asEP_DISALLOW_VALUE_ASSIGN_FOR_REF_TYPE is definitelly going to be set TRUE in my project

In Topic: What's everyone doing with Angelscript!

09 May 2013 - 04:07 PM

Thanks, I do understand the left hand requirement, I just got surprised by the @ on right side of assignment. Anyway, it is logical.

In Topic: What's everyone doing with Angelscript!

08 May 2013 - 09:07 PM

The script works like a charm in the development version (plugged it all today). I started from your texture generator demo, creating similar image class, not realizing the library changed a bit from there... but I got my bearings very quickly.


One thing I would like to have more explained is the typing convention with the reference sign @.

say you have

void function(image @img)
image@ img = @image(200,200);
is this @ on the function(@img) just for convention? Because it works as function(img) as well.
Same with the 
image@ img = @image(200,200);
omitting the @ from the front of image(200,200) works as well and seems to not do anything different, but is there any difference or it is all for convention?

Attached File  angelscript.jpg   92.68KB   35 downloads

In Topic: What's everyone doing with Angelscript!

07 May 2013 - 09:20 PM

I am working on a nodal graphical software Photo-Reactor and after three days of messing with the angelscript, I am 100% positive this will become a great part of the software.

I previously contemplated to write my own bytecode interpreter as nothing I found was suitable and I need both 32 and 64 bit version. I am absolutely glad I spent the time looking around, the angelscript is exactly what I was after. Big kudos to Andreas. The angelscript is a beast. What I love the most is that it is c/c++ syntax and it is brilliantly plug-and-play.

More about the project: