Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions

[Avi Kivity]

On 12/15/2011 04:21 PM, Paolo Bonzini wrote:
>
>>   cpu-common.h     |   36 -----------------------------
>>   exec-obsolete.h  |   66
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   exec.c           |    3 ++
>>   hw/etraxfs_eth.c |    3 --
>>   memory.c         |    3 ++
>>   5 files changed, 72 insertions(+), 39 deletions(-)
>>   create mode 100644 exec-obsolete.h
>
>
> I would prefer exec-private.h or memory-private.h.  Right now, the
> situation is that exec.c provides a low-level interface to memory.c. 
> If the situation changes, the header will disappear.

Since the header is going to disappear, does it really matter?  I plan
on removing it long before 1.1.

-- 
error compiling committee.c: too many arguments to function