Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Nokia (NOK) -- Ignore unavailable to you. Want to Upgrade?

To: 49thMIMOMander who wrote (21084)	7/10/2002 4:55:25 PM
From: Quincy	Read Replies (2) \| Respond to of 34857

Matsushita? Matsushita needs to avoid reinventing application code for handsets that don't have Brew or the computing power for Java. "Btw, does BREW support threadlock, overflowing buffers, stacks and resources, wild and lost pointers?? (or do they just happen, freely and ultimately, like a fart in the desert??)" I was referring to process threading on the server side, not the handset side. (ed: oops.) Bounds checking and garbage collection may be automatic and sometimes out of control in Java. But, it is not impossible in C, C++, or Brew. I actually like being in control of my own malloc.