Skip to content

EliteTK/vav

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

VAV

About

Very Awesome Vectors (VAV) is an attempt at implementing vectors in C, but doing so in a manner that doesn't look like something a dog chewed on.

There are issues with VAV and an overall issue about its implementation, these issues are detailed below.

Currently, I have no clue how large vectors can be but the vector length stored in the header can get up to 9223372036854775807. The limit is then made smaller by the check for a heap overflow and possibly even smaller because of the use of variadic macros. However, I can guarantee a length of up to 60 which should be about 56 more than anyone ever needs.

If you're familiar with SDS you might think that VAV sounds a bit like SDS, in fact, I first had this idea before I knew about SDS, but seeing SDS in practice persuaded me to put this idea to (virtual) paper.

Quick Run-down

Copy vec.c and vec.h into your project, use vec(your, vector, here) to create a new vector, this returns a float pointer, this is to allow the use of array indices with the vectors.

vec_cross and vec_dot should be self explanatory for anyone who knows anything about vectors (vec_cross only works on vec3). They both take two parameters and dot / cross the respective vectors together.

vec_len will return the length of the vector. (vec_dot(vector, vector) is an easy way to get the length squared.)

vec_addm takes three parameters, vector_a, vector_b and multiplier. vec_addm returns vector_a + vector_b * multiplier.

vec_norm returns the normalised vector.

vec_blank takes one parameter of length and creates a completely zeroed vector of that length.

vec_new is the raw function for creating vectors, it takes a parameter of length, and a float pointer containing the initial values. vec_del can then be used to deallocate the resulting vector.

vec_deltemp will only delete temporary vectors and currently has little use.

vav_temp and vav_perm set the vector to be temporary or permanent respectively.

Quick Example

Here's a quick example of how to take the cross product of (3, 5, 2) and (-1, 3, 4) and perform a dot product with the output of that cross product and the vector (10, -4, -1).

vec_dot(vec_cross(vec(3, 5, 2), vec(-1, 3, 4)), vec(10, -4, -1));

Yes, all of that, on one line, and no memory leaks. "How is this possible?" You might ask. Well, every vector stores, in its header, a singly bit value defining whether it is temporary. A temporary vector, when passed to a VAV function, will be freed or reused for the result of that function. This means that the above only uses 3 mallocs, one for each initial vector.

Technicalities

Right now VAV uses a 64 bit header containing the length (64 bits) and the temporary state (1 bit).

The implementation of the vec() macro means that it can figure out how many arguments you pass it.

Future Plans

There are plans to rename all the functions into something shorter and more vav oriented, for example: vav_c, vav_d, vav_l, vav_a and vav for the most used stackable functions. Or possible even v_c, v_d, v_l and v but really, this is a drop in solution, want something different? Just changed it.

Issues

Sadly, VAV has some issues, the biggest two issues are a lack of error reporting and the fact that VAV uses malloc for every vector.

The first issue makes it unusable in any kind of real application and the second issue makes VAV slow.

VAV still makes sense to use when prototyping some kind of vector application, but it really makes far more sense to start off using a good vector implementation to begin with. In reality, nobody really needs 1000 element vectors. You just need 2, 3 and 4 element vectors and then some good matrices.