Uhm... not sure if the variable naming will actually do what it's supposed to. Say you write a function to which you can pass on several variables:
Code:
myFunc local.fVar local.vVar:
end
Now, if we use the varname command to convert it to a string, it won't tell us for sure that fVar is a float. Because we used "fVar" in the receiving function with the expectation that fVar will be a float.
This defeats the purpose. It would only work by either returning every single reference pointer (vars, targetname..) in the engine for the same piece of data or by returning the variable's name in the linking/previous thread.
And if this is only for the assumption that fVar is a float or vVar is a vector, then why can't we just name the variables whatever we like and still work with regards to the expected type of variable.
Originally Posted by
RazoRapid
* Reading whole file into text variable (string)
* Saving whole string variable into file
These two will be very fast because they will use byte operation, so you will need to open a file in binary mode to use them. Then you can parse the string, etc. It's good when you don't have to update certain lines of the file but just write or read it all.
* Move/Rename file
* Remove file
* Copy file
* File exists
Some handy stuff
* sin, cos, tan, tan2, asin, acos, atan, sinh, cosh, tanh, exp, log, log10, pow, sqrt, and some more, they will be faster and more precise, but we'll still create wrappers for them in our libs
Awesome stuff. I can't wait. But don't strings have a maximum capacity of 1024 chars? When text in the file is longer than 1024 chars, how are you going to circumvent that?