[v1.2.4 - Nov 2nd] ACS.NET - Useful ACS functions!

[Vincent(PDP)]

ACS.NET
Created by: Visual Vincent

Original thread: http://zandronum.com/forum/showthread.php?tid=5666

What is this?
ACS.NET is an ACS library for Zandronum/ZDoom where I've implemented some functions that are similar to those in the .NET Framework.
Of course there is more than just .NET Framework functions, this is a library with a bunch of useful functions for ACS.

Well, I guess the above explains it pretty much...
A list of all available functions and how to use them can be found in the original thread: http://zandronum.com/forum/showthread.php?tid=5666


Case sensitivity
Sadly all find/replace functions are case sensitive, which means that when for example searching for the string "wood" in "woodchuck", "wood" must have the same casing as the "wood" in "woodchuck". So for example "Wood" or "WOOD" or "WooD" won't match.

Also note that most of the search/replace functions are capable of finding whole strings and not just characters (letters)!


Download

Download from mydoomsite.com

Download from mydoomsite.com (Example WAD)


Changelog
v1.2.4
* Fixed so that ParseInt and ParseFloat supports parsing of negative numbers.
* Included Math_Abs with the library (required for ParseFloat to work).

v1.2.3
* Added a ParseFloat function to parse strings to fixed point!

v1.2.2
* Fixed bugs with StringReplace and StringSubstring. (I.e StringReplace won't replace text if it's in the very end of the string)
* Added a ParseInt function to parse/convert strings to integers!

v1.2.1:
* Removed the Math_PI, Math_e, IntegerMinValue, IntegerMaxValue functions and replaced them with macros. (#LibDefine)
Note that the macros still have the same name as the functions.

v1.2.0:
* Added tons of new functions!
* Updated the example WAD.
* Bug fixes.


Example WAD in action!

---

Problems or suggestions?
If you are experiencing any problems with this library, OR if you just have got any suggestions regarding it (i.e implementation suggestions, fixes etc.):
Contact me on this forum or on support@mydoomsite.com

The above applies for questions and help too.

Have fun!

[Nash]

Sick! Will definitely check this out soon.

[Vincent(PDP)]

Sick! Will definitely check this out soon.

I would really like your opinion about it. No one has said what they think, yet.
-------------------------------------------------------------------------------------------------------------------------
I updated the library in order to make the Math_PI, Math_e, IntegerMinValue and the IntegerMaxValue functions into macros/constants instead. (#LibDefine)

[Apothem]

Yup, I knew this was possible for years. I knew I shoulda posted my source for my memory management tool a while ago. I suppose I should make a thread for it lol.

[Vincent(PDP)]

Yup, I knew this was possible for years. I knew I shoulda posted my source for my memory management tool a while ago. I suppose I should make a thread for it lol.

If you know your loops, those functions are possible yes.

What does your memory management tool do? o.o

[Vincent(PDP)]

Updated the library to v1.2.2!

Updates:
* StringReplace and StringSubstring bugfixes.
* Added the new function ParseInt to be able to convert strings to integers!

[Vincent(PDP)]

A small little update, requested by Nash...

v1.2.3:
Added a ParseFloat function to parse strings to fixed point!

[Vincent(PDP)]

Okay... Another, somewhat critical, update.
When I first created ParseInt, I forgot to make it able to parse negative numbers...

v1.2.4:
* Fixed so that ParseInt and ParseFloat supports parsing of negative numbers.
* Included Math_Abs with the library (required for ParseFloat to work).

[Nash]

Thank you so much for the continued support. Have you considered what I said about the Float/Fixed naming convention? Or do you think it doesn't matter? :D

[Vincent(PDP)]

Thank you so much for the continued support. Have you considered what I said about the Float/Fixed naming convention? Or do you think it doesn't matter?

Personally I like "ParseFloat" better than "ParseFixed"... So I'm afraid that's a no to that one. :/

[Nash]

No problem! :D It's not a showstopper. If I ever switch to GDCC, I guess I could just rename it back to ParseFixed (and just mentioning it here for completeness' sake, because GDCC has an actual float type that is different from the fixed type).