Linked by kragil on Wed 23rd Jan 2013 20:26 UTC
Google "Native Client enables Chrome to run high-performance apps compiled from your C and C++ code. One of the main goals of Native Client is to be architecture-independent, so that all machines can run NaCl content. Today we're taking another step toward that goal: our Native Client SDK now supports ARM devices, from version 25 and onwards."
Thread beginning with comment 550454
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by Laurence
by henderson101 on Fri 25th Jan 2013 13:19 UTC in reply to "RE[7]: Comment by Laurence"
Member since:

Another solution used in languages like C#, Modula-3, Oberon family or D, is to allow in a very controlled way to request and release memory from the runtime.

I remember a co-worker driving himself insane with CF1.0 and SqlClient. Somewhere is wasn't releasing memory correctly and basically using up all the free memory on the device. In the end, he put a number of explicit GC.Collect()'s in the code. It was a documented bug, I think it was fixed in CF2.0, but we had to use 1.0 because the devices being used didn't support 2.0 (IIRC, they were mixed, some were running PocketPC 2000 or something like that... plus most had bugger all RAM.)

Reply Parent Score: 2