New iterator things!

iterator container::end() //returns an iterator that points at the end, useful for...
bool iterator::operator==(const iterator &in) //checking if your iterator equals end
bool iterator::IsEnd() //check it with 1 c++ function call and no need for creating another iterator object

bool container::erase(const iterator &in) //erase at iterator, returns true if something was erased (if iterator was not end)
size_t container::erase(const iterator_range_begin &in,const iterator_range_end &in) //erase a range, returns amount of things erased

//non map containers
iterator container::find_iterator(const value &in) //find that returns an iterator, returns end if not found

//vector and list
void container::insert(const iterator &in, const value &in) //insert before iterator, using end iterator will insert at the end

//map / uo_map
iterator container::find_iterator(const key &in) //find that returns an iterator, returns end if not found

.

As usual, you can change all the names in the config. If you don't like the nonstandard "value find(value,bool& success", you can name that to "nonstd_find" and name "find_iterator" to just "find".

No reverse iterators yet.

Also made some architecture changes to the c++ side of things, more templates, less nasty preprocessor names.

Theres a bit of a safety problem with iterators right now:

If a container is modified, all of it's currently existing iterators become invalid and using them will crash. I got some plans for more iterator safety, but it didn't make it to this build.

New stuff available in the new branch "experimental". ZIP

/*
  Every operation that changes a container increments a version number.
  If you try to access an iterator and it's version number differs from the container's, an exception will be thrown.
  Without this, illegal access will crash.
  This obviously reduces runtime performance.
*/
#define aatc_CONFIG_ENABLE_ERRORCHECK_ITERATOR_SAFETY_VERSION_NUMBERS 1

With this thing on, this code will cause exceptions instead of crashing:

vector<int> cont;

cont.push_back(1);
cont.push_back(2);
cont.push_back(3);
cont.push_back(4);
cont.push_back(5);

auto it = cont.find_iterator(3);

cont.erase(it);
cont.erase(it);//this line will cause an exception, because the previous erase modified the container

for(auto it = cont.begin(); it++;){
  Print("value = " + it.value);


  if(it.value == 4){
    //modify the container
    //this line will work here, but any iterator access or incrementing after it will cause an exception
    cont.push_back(123);
  }
}

You can custom tune your exception messages in the config:

/*
  Happens when trying to access or set an iterator and the container has been modified after iterator construction.
*/
#define aatc_errormessage_iterator_container_modified "Invalid iterator. Container has been modified during iteration."

/*
  Used by the container if it tries to use an invalid iterator.
  Example of erasing twice with the same iterator:
    vector<int> myvec;
    //add 1 2 3 4 5 to vector
    auto it = myvec.find_iterator(3);
    myvec.erase(it);
    myvec.erase(it);//this line will cause this exception, because the first erase changed the container state and invalidated all iterators
*/
#define aatc_errormessage_container_iterator_invalid "Invalid iterator."

Available in the experimental branch.

	map<Object@, Object@> myMap;
	if (@myMap[@key] == null)
		//Found an empty handle

The operand is implicitly converted to handle in order to compare them at row: X col: Y

    map<Object@, Object@> myMap;
    Object@ obj = myMap[@key];
    if (@obj == null)
	//Found an empty handle

The warning is gone, and everything still works as expected.

I'm using the AATC master as it is on GitHub and Angelscript Version 2.29.1
Is this a parse error? Binding problem ? Or am I doing something wrong?

Thanks again for this great Addon btw ;)

By the way friends, I have recently made a refactoring of the library that puts everything inside namespaces and adds a convenient interface to create and manipulate AATC containers in c++. Before this using the containers in c++ was outrageously inconvenient due to too many c++ templates getting in the way. Now you can conveniently pass containers between c++ and angelscript and make use of them in c++ without 400 templates getting in your way.

The refactor was born of this github issue.

There's a bit of documentation available in the last post of the issue too.

The c++ side now makes use of metaprogramming techniques such as tag dispatch instead of std::conditional to achieve c++ side convenience. This makes it easier for AATC to support additional container types and somewhat reduces template smell.

The config file looks quite different because most options are now proper variables (not macros) and neatly organized inside namespaces. Some macros still remain.

I haven't merged the refactor to the master branch yet because it is quite the breaking change due to the new namespaces breaking literally all old names (in c++, not angelscript).

I have tested the refactor with ye olde AATC tests and my game project. Seems to work good with only minor name changes.

The angelscript side interface has no major changes. Some default method names have been consolidated a bit (insert_position_before -> just insert, erase_position_range & erase_position -> just erase) etc. They can be changed right back in the config if you like the long names or have a grudge against function overloading.

The refactor is available in its own github branch for now. Before merging to main / creating full documentation I would like some reviews from users / Andreas.

Does it work with your projects?

Did I manage to remove some feature you were using?

Is the c++ code more comprehensible?