var is also impractical when it comes to vector calculations. Calculating dot products for example is only possible with small-magnitude vectors. This is indeed somewhat annoying. I neather want to typecast between float and var all the time, nor I want to use my own vector functions. AFAIK converting floating point numbers to integer types in C is (or was) for some reason a pretty slow process on Pentium machines. I don't know whether this still applies to lite-C, though.

However, Gamestudio has the reputation of being a program with very good backward compatibility. Replacing var with float will easily break this backward compatibility completely. var is not only used for fixed point numbers, but also for storing engine object handles and pointers. Entity skills are vars, too. So replacing alone won't do it.

Even though I would appreciate a change-over to standard C data types, I consider "abandoning the var type soon" unlikely at the moment. Might be a wrong estimate, though.

I wonder how realistic it would be to ask for a #define, then, that enabled the switch?

Jibb

definitely agree!
Never in history something was as unecessary as inventing the var-type.

Float was just a suggestion because var's are used most often for numeric stuff. If you only have integer values - use integer. If you return pointers, return them in the appropriate format or use simply void* (e.g. for sound handles or do typedef void* SOUND_HANDLE or else).

Vars must be replaced with double, not float. Replacing them with float would lose precision with large numbers, so thats the opposite of what you want. But I think double will work for all coordinate ranges without losing precision.

It wont be backwards compatible of course, but rewriting scripts for double vars should be not to difficult. Sometimes it could be tricky but in most cases the vars only need to be replaced with int, or with pointers, depending on what you do with them.

Its similar to the step from C-Script to lite-C.

with floats you don't need that big numbers though since they are much better suited for directly using them as (much more intuitive) meters instead of 32 quants = 1 meter, or 1 quant is 1 inch or something like that.

but if i remember correctly lite-c doesn't really fully support floats anyway (my memory about this is fuzzy but didn't a lot of stuff always require casting to double?) so doubles would be fine too.

You would not like it when we replaced var with floats, and let you then deal with lots of problems like reduced precision, failing of comparison operations and so on. Rewriting your scripts would be a nightmare, much worse than the rewriting WDL code to C. Vars will stay.

But using floats and doubles for vector and matrix operations makes a lot of sense and you're free to do that - the whole DirectX vector and matrix library can be used with lite-C. The function list can be found in the DirectX documentation. The DirectX functions are sometimes even faster than their vec_ counterparts.

Ok, that makes some sense. But could you at least overload some functions, that internally cast the vars to other types anyway, such as e.g. file_asc_write, where char would make much more sense?

All C languages automatically convert numbers and numerical variables. You don't need overloading for this.

I know, but it kind of feels wrong to take a char, cast it to var, and then cast it back to char. This is also a small performance loss.