- Sun Oct 14 19:45:54 PDT 2001

[libfaim.git] / include / faimconfig.h

diff --git a/include/faimconfig.h b/include/faimconfig.h
index 84dc448552e4357bb1c26752154deeac4e9eaaf3..64987030bacdae005e0120a7e9cb3269a67726b0 100644 (file)
--- a/include/faimconfig.h
+++ b/include/faimconfig.h
@@ -39,31 +39,6 @@
 #define FAIM_LOGIN_SERVER "login.oscar.aol.com"
 #define FAIM_LOGIN_PORT 5190
 
-/*
- * What type of synchronisation to use.
- * 
- * We don't actually use threads, but can use the POSIX mutex
- * in order to maintain thread safety.  You can use the fake locking
- * if you really don't like pthreads (which I don't) or if you don't
- * have it.
- *
- *   USEPTHREADS - Use POSIX mutecies
- *   USEFAKELOCKS - Use little stub spinners to help find locking bugs
- *   USENOPLOCKS - No-op out all synchro calls at compile time
- * 
- * Default: use noplocks by default.
- *
- * !!!NOTE: Even with USEPTHREADS turned on, libfaim is not fully thread
- *          safe.  It will still take some effort to add locking calls to
- *          the places that need them.  In fact, this feature in general
- *          is in danger of being officially deprecated and removed from 
- *          the code.
- *
- */
-#undef FAIM_USEPTHREADS
-#undef FAIM_USEFAKELOCKS
-#define FAIM_USENOPLOCKS
-
 /*
  * Size of the SNAC caching hash.
  *