1 files changed, 2 insertions, 16 deletions
diff --git a/src/ll.h b/src/ll.h
index 4b5a2df..154cfe2 100644
--- a/src/ll.h
+++ b/src/ll.h
@@ -1,25 +1,11 @@
 #ifndef __VXGG_REWRITE___LL_H___305861098005___
 #define __VXGG_REWRITE___LL_H___305861098005___
-/*//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
+// Notice: dlinked functions are no longer necessarily xalloc, but MAY be IF the `___VXGG___USE_XALLOC_FOR_VALLOC___` is greater than 0
-// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
-// RNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING  //
-// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////*//* 
-//                                                                                                                                //
-// dlinkedlist functions should be considered X_ALLOC functions, as they call xcalloc to initialize new nodes. This is not        //
-// reflected in their naming, which could change later, but as of now it is something to keep in mind. This means ABSOLUETLY NO   //
-// USE OF DLINKEDLIST FUNCTIONS INSIDE ENCRYPTION FUNCTIONS, OR ANYTHING THAT SHOULD BE CONSIDERED ATOMIC OR SEMI-ATOMIC. IF      //
-// XCALLOC ERRORS FOR ANY REASON, AND YOU'RE DOING SOMETHING WITH THESE IN AN (SEMI)ATOMIC FUNCTION, YOU WILL BREAK SHIT          //
-//                                                                                                                                //
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////*//*
-// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
-// RNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING  //
-// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
-//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////*/
 /* TODO: Implement a way to register a set of alloc functions to a linked list so I can give it arenas for memory allocation
 // instead of just xcalloc */
+    // I don't know if I care to do this right now. I might be able to hack it in but it would be a fugly hack, something as bad if not worse than that weird callback thing I was doing with the ALWAYS_CHECK_LIBSODIUM macro
 typedef void (*dll_freecb)(void*);
 typedef struct dlinked dlinkedlist;

diff --git a/src/ll.h b/src/ll.h index 4b5a2df..154cfe2 100644 --- a/src/ll.h +++ b/src/ll.h
@@ -1,25 +1,11 @@
1	#ifndef __VXGG_REWRITE___LL_H___305861098005___	1	#ifndef __VXGG_REWRITE___LL_H___305861098005___
2	#define __VXGG_REWRITE___LL_H___305861098005___	2	#define __VXGG_REWRITE___LL_H___305861098005___
3		3
4	/*//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////	4	// Notice: dlinked functions are no longer necessarily xalloc, but MAY be IF the `___VXGG___USE_XALLOC_FOR_VALLOC___` is greater than 0
5	// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
6	// RNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING //
7	// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
8	//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
9	// //
10	// dlinkedlist functions should be considered X_ALLOC functions, as they call xcalloc to initialize new nodes. This is not //
11	// reflected in their naming, which could change later, but as of now it is something to keep in mind. This means ABSOLUETLY NO //
12	// USE OF DLINKEDLIST FUNCTIONS INSIDE ENCRYPTION FUNCTIONS, OR ANYTHING THAT SHOULD BE CONSIDERED ATOMIC OR SEMI-ATOMIC. IF //
13	// XCALLOC ERRORS FOR ANY REASON, AND YOU'RE DOING SOMETHING WITH THESE IN AN (SEMI)ATOMIC FUNCTION, YOU WILL BREAK SHIT //
14	// //
15	//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
16	// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
17	// RNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING //
18	// BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WARNING BIG WA //
19	//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////*/
20		5
21	/* TODO: Implement a way to register a set of alloc functions to a linked list so I can give it arenas for memory allocation	6	/* TODO: Implement a way to register a set of alloc functions to a linked list so I can give it arenas for memory allocation
22	// instead of just xcalloc */	7	// instead of just xcalloc */
		8	// I don't know if I care to do this right now. I might be able to hack it in but it would be a fugly hack, something as bad if not worse than that weird callback thing I was doing with the ALWAYS_CHECK_LIBSODIUM macro
23		9
24	typedef void (dll_freecb)(void);	10	typedef void (dll_freecb)(void);
25	typedef struct dlinked dlinkedlist;	11	typedef struct dlinked dlinkedlist;