bob wrote: > Yes, malloc and free are oldies but goodies. > Uhhh ...
> I remember meeting malloc back in like 1991. It didn't want to give me more than 64k back then, but it is nicer to me now. Fond reminiscence doth not a sound engineering basis make. I find the suggestion to switch to native code and use malloc and free ridiculous. You use native code when a service only available there is needed, and malloc/free when native code requires it. How does that translate to this Android question? > Lew wrote: > bob wrote: > >> Maybe you can use native code and use malloc and free? >> > > Really? > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
