XAV-- (formally known as XAV4) is the forth generation of the XAV coding language, built off XAV++ (formally known as XAV3) XAV-- has many things to offer! including: proper local containers .upper (thanks to @scratchVSTAR) .starts_with() and more! ========================================= Documentation: XAV-- is in alpha, no documentation is needed yet. ========================================= Dev team: @Xplayer_maker @scratchVSTAR ========================================= IDE: the XAV++ IDE is compatible with XAV-- so you can use it to code XAV-- code https://error-xmakernotfound.github.io/XAV-IDE/ ========================================= Tags: #XAV-- #XAV #coding_language #coding #language #madebyxmaker
Update logs: XAV 4.01: the first integration of XAV--, added .upper .starts_with added local functions and containers, and fixed a small list bug. XAV 4.02: Added inherit and mutate, now allowing local variables from an above runtime to be used in functions, and change local variables from above as well! XAV 4.03: Removed mutability for functions, changed the formatter to flatten parentheses, changed inherit and mutate so they can inherit/mutate multiple locals at a time eg: inherit x, y;mutate x, y;, changed the resolver to work properly with lists coming from function inputs, added struct making storing values much more organised; since it uses keys instead of numbers as indexes, fixed void not removing variables after mutate was called, changed list storage and calls to store the data as an array (["item one", "item two"]) instead of encoding the Current Working Array list, this made it faster at the same time while allowing Array to be inserted into Array as a literal instead of passing a pointer eg: Array x used to be passed as the pointer (x) but now is passed as (["hello ", "world"]), I have no idea how i managed to do this without encountering any bugs on the way XD. XAV 4.04: fixed an Array bug that made arrays in arrays unstable and in most cases; unusable, changed the resolver so doing something like print([[1.add(1)]].item(1).item(1)); wouldn't give it a panic attack (the fix was easy, took me two minutes to find and fix lol), removed and added a bunch of stuff related to Arrays (there's too much to list here), fixed a block bug, removed the array keyword, because i realized that you could just do {local myarray([])} or {global myarray([])} or {omnipresent myarray([])} which basically made the array keyword useless XD, fixed a struct bug.
