From: normalperson@...
Date: 2014-07-23T07:22:51+00:00
Subject: [ruby-core:63954] [ruby-trunk - Feature #10082] [PATCH] add ZALLOC* macros to reduce ALLOC + MEMZERO calls

Issue #10082 has been updated by Eric Wong.


 tad.a.digger@gmail.com wrote:
 > The basic policy of patch feels great, but why don't you name CALLOC?
 > 
 > I feel CALLOC is more straitforward because calloc(3) is in the standard and
 > ZALLOC(_N) already uses calloc().
 
 I considered ZALLOC_N == CALLOC, but the arguments are reversed
 for calloc(3), so I didn't want to risk that confusion, either.
 
 I chose ZALLOC based on kzalloc/kmem_cache_zalloc in the Linux kernel.
 
 On a related note: maybe RB_ZALLOC or RUBY_ZALLOC would be better, but
 that would be inconsistent with existing ALLOC(_N) and REALLOC_N, too.
 
 Naming is hard :<
 
 matz/ko1 can make the final decision.
 
 I'll commit in a day or so if we cannot decide, the name may still
 change after commit.

----------------------------------------
Feature #10082: [PATCH] add ZALLOC* macros to reduce ALLOC + MEMZERO calls
https://bugs.ruby-lang.org/issues/10082#change-47975

* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: Koichi Sasada
* Category: core
* Target version: current: 2.2.0
----------------------------------------
This reduces code and binary sizes.
ZALLOC macros are accessible via public API for exts

OK to add this API?  It should simplify some code and reduce typos.


---Files--------------------------------
zalloc.patch (7.4 KB)


-- 
https://bugs.ruby-lang.org/