Re: [classlib] mem

(sorry for the very late response) Geir Magnusson Jr wrote: I don't mind the macros, I just think the actual function should be named something different than the macro and have some docs to stem confusion from other readers in the future. Yea/nea? Yea to doc (thanks!) and nea to renaming.

RE: [classlib] mem

-Original Message- From: Tim Ellison [mailto:[EMAIL PROTECTED] Sent: Thursday, July 06, 2006 12:34 PM To: harmony-dev@incubator.apache.org Subject: Re: [classlib] mem (sorry for the very late response) Geir Magnusson Jr wrote: I don't mind the macros, I just think the actual

Re: [classlib] mem

Magnusson, Geir wrote: -Original Message- From: Tim Ellison [mailto:[EMAIL PROTECTED] Sent: Thursday, July 06, 2006 12:34 PM To: harmony-dev@incubator.apache.org Subject: Re: [classlib] mem (sorry for the very late response) Geir Magnusson Jr wrote: I don't mind the macros, I

Re: [classlib] mem

Geir Magnusson Jr wrote: Tim Ellison wrote: This function is (deliberately) not exported from the hyprt.dll so you cannot call it directly. You have to call it via the function pointer table ... That's the missing element - it's not exported. The idea is that code should always go via the

Re: [classlib] mem

Tim Ellison wrote: Geir Magnusson Jr wrote: Tim Ellison wrote: This function is (deliberately) not exported from the hyprt.dll so you cannot call it directly. You have to call it via the function pointer table ... That's the missing element - it's not exported. The idea is that code

Re: [classlib] mem

Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so, they are the same indeed, and the later is the a macro. Everytime before

Re: [classlib] mem

Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so, they are the same indeed, and the later is the a

Re: [classlib] mem

Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so, they are the same indeed, and the later is the

Re: [classlib] mem

Tim Ellison wrote: Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so, they are the same

Re: [classlib] mem

Paulex Yang wrote: Tim Ellison wrote: snip PORT_ACCESS_FROM_PORT(portlib)- you have a portlib ptr So in the scenario of multiple HyPortLib instances, it can be used to specify which one to use? You are right, when you have multiple instances the simple macros do not help and you need

Re: [classlib] mem

Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? Well, the one I'm looking at is hymem.c void

Re: [classlib] mem

Tim Ellison wrote: Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so, they are the same indeed,

Re: [classlib] mem

Geir Magnusson Jr wrote: Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? Well, the

Re: [classlib] mem

Geir Magnusson Jr wrote: Tim Ellison wrote: Jimmy, Jing Lv wrote: Geir Magnusson Jr wrote: Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) Hi Geir: Not sure if the later is hymem_allocate_memory(int size)? If so,

Re: [classlib] mem

Oliver Deakin wrote: Also defined in hyport.h is hymem_allocate_memory(param1) (the single param function Jimmy was talking about) which is a macro defined to be: privatePortLibrary-mem_allocate_memory(privatePortLibrary, param1). Ah. Thanks. I didn't see that. I'll continue answering

Re: [classlib] mem

Tim Ellison wrote: Geir Magnusson Jr wrote: Except... 1) They aren't as Jimmy suggests, at least the one's I'm looking at. 2) the implementation in hymem.c just calls malloc() I'm confused. Hopefully you are no longer confused after Oliver's explanation. Yes, although I am still

Re: [classlib] mem

Geir Magnusson Jr wrote: Tim Ellison wrote: Geir Magnusson Jr wrote: Except... 1) They aren't as Jimmy suggests, at least the one's I'm looking at. 2) the implementation in hymem.c just calls malloc() I'm confused. Hopefully you are no longer confused after Oliver's explanation. Yes,

Re: [classlib] mem

Tim Ellison wrote: Geir Magnusson Jr wrote: Tim Ellison wrote: Geir Magnusson Jr wrote: Except... 1) They aren't as Jimmy suggests, at least the one's I'm looking at. 2) the implementation in hymem.c just calls malloc() I'm confused. Hopefully you are no longer confused after Oliver's

[classlib] mem

Why would I use portLib-mem_allocate_memory(portLib) over just calling hymem_allocate_memory(portlib, ) geir - Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED]