Quietly eliminating varargs to mps_alloc. they were never documented.

Copied from Perforce
 Change: 181843
 ServerID: perforce.ravenbrook.com

2 files changed, 4 insertions, 6 deletions

diff --git a/mps/code/mps.h b/mps/code/mps.h
index 1eb0f230689..a04d26340de 100644
--- a/mps/code/mps.h
+++ b/mps/code/mps.h
@@ -425,7 +425,7 @@ extern mps_res_t mps_chain_create(mps_chain_t *, mps_arena_t,
                                   size_t, mps_gen_param_s *);
 extern void mps_chain_destroy(mps_chain_t);
 
-extern mps_res_t mps_alloc(mps_addr_t *, mps_pool_t, size_t, ...);
+extern mps_res_t mps_alloc(mps_addr_t *, mps_pool_t, size_t);
 extern mps_res_t mps_alloc_v(mps_addr_t *, mps_pool_t, size_t, va_list);
 extern void mps_free(mps_pool_t, mps_addr_t, size_t);
 
diff --git a/mps/code/mpsi.c b/mps/code/mpsi.c
index a0427a5c150..746ba3e712d 100644
--- a/mps/code/mpsi.c
+++ b/mps/code/mpsi.c
@@ -26,10 +26,6 @@
  * check that protocols are obeyed by the client.  It probably doesn't
  * meet checking requirements.
  *
- * .varargs: (rule.universal.complete) The varargs passed to
- * mps_alloc(_v) are ignored at the moment.  None of the pool
- * implementations use them.
- *
  * .poll: (rule.universal.complete) Various allocation methods call
  * ArenaPoll to allow the MPM to "steal" CPU time and get on with
  * background tasks such as incremental GC.
@@ -677,7 +673,7 @@ void mps_pool_destroy(mps_pool_t pool)
 }
 
 
-mps_res_t mps_alloc(mps_addr_t *p_o, mps_pool_t pool, size_t size, ...)
+mps_res_t mps_alloc(mps_addr_t *p_o, mps_pool_t pool, size_t size)
 {
   Arena arena;
   Addr p;
@@ -709,6 +705,8 @@ mps_res_t mps_alloc(mps_addr_t *p_o, mps_pool_t pool, size_t size, ...)
 }
 
 
+/* mps_alloc_v -- allocate in pool with varargs.  Deprecated in 1.112. */
+
 mps_res_t mps_alloc_v(mps_addr_t *p_o, mps_pool_t mps_pool, size_t size,
                       va_list args)
 {