SNF Release: 0.0.2-alpha
❔Don't know what SNF is? Check this post. What's in this
Currently this version is made as a step forward from a simple proof-of-conept into an actual usable library, although still not perfect and buggy, it's still one step towards that, Revamped core parts, Added new features.. etc.
INVALID
(0x00): UNIMPLEMENTED_OPCODE
(0x02):
📖 Documentation: /snf/c/0.0.2-alpha
📂 File(s): 0.0.2-alpha-snf-c.tar.gz
(Source code)
( See below for installation tutorial)
✨(new) Added a new variable system: Variables are now stored in a specific structure inside <SNF/vars.h>
instead of them being scattered around multiple headerfiles.
✨(new) Added OPCode Command Functions: which means when you create new OPCode structure you can link function to OPCode Command, hence allowing the use of Custom OPCodes fully,
✨ Revamped Thread pool system
work
to do, which added CPU Time and latency, so after Reading this Wikipedia Page (Last visited on Augest 2, 2024 at 2:37 PM GMT +1). I noticed that I should've created the threads At once and from the beggining. so I did just that in this update and it did do wonders.⚒️ Moved Base OPCode Commands' Response handling from being built-in inside the client handling, into their own functions in the <SNF/cmds.h>
file.
⚙️ Improuved Client handling & bug fixed related to it.
⚙️ Improuved Documentation
⚙️ Improuved Makefile in the following
make cleanlib
: cleans the shared library binary ( Requires root access )make t_<Test File>
make buildtest
: Now builds tests with Address Sanitizer on by default ( Doesn't include make gdbt_<Test File>
)♻️ Renamed <SNF/locate3.h>
➡️ <SNF/lookup3.h>
, Due to a mistake ( Lookup3 being the appropriate name )
📖 Documentation: /snfclient/dotnet/0.0.2-alpha
📂 File(s): 0.0.2-alpha-snfclient-dotnet.dll
(Binary)
( See below for installation tutorial)
SNFClient.Exception.OPCode.Unregistred
: Thrown when an SNFClient.OPCode.Member
was not registred but used either by the client or the server.RequestResponseCB(Request Response)
➡️ RequestCB(Request Response)
in SNFClient.Callbacks
: The naming of delegates is related to it's parameters and not it's use case, this to avoid making two delegates that serve their own usecase but require matching parameters