Browse files

Adding a new item (number 11) that explains why it's important to use

emalloc() and friends in place of the standard C library functions.
  • Loading branch information...
1 parent 2f88f50 commit e79772d6e047b56a018ce3d295c552c12092bcd2 @jparise jparise committed Oct 10, 2002
Showing with 13 additions and 0 deletions.
@@ -122,6 +122,19 @@ Exceptions:
existing. End users should use function_exists() to test for the
existence of a function
+[11] Prefer emalloc(), efree(), estrdup(), etc. to their standard C library
+ counterparts. These functions implement an internal "safety-net"
+ mechanism that ensures the deallocation of any unfreed memory at the
+ end of a request. They also provide useful allocation and overflow
+ information while running in debug mode.
+ In almost all cases, memory returned to the engine must be allocated
+ using emalloc().
+ The use of malloc() should be limited to cases where a third-party
+ library may need to control or free the memory, or when the memory in
+ question needs to survive between multiple requests.
Naming Conventions

0 comments on commit e79772d

Please sign in to comment.