Recent Changes - Search:


Users


Developers

edit SideBar

SharedMemoryByteSlice

Developers.SharedMemoryByteSlice History

Show minor edits - Show changes to markup

May 03, 2007, at 07:18 PM by 24.6.247.48 -
Changed lines 1-5 from:

[url=http://www.mp3bud.net/Laura-Pausini.html]Laura Pausini[/url] [url=http://www.mp3bud.net/ATB.html]ATB[/url] [url=http://www.mp3bud.net/Whitney-Houston.html]Whitney Houston[/url] [url=http://www.mp3bud.net/Moody-Blues.html]Moody Blues[/url] [url=http://www.mp3bud.net/Cascada.html]Cascada[/url]

to:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the data is considered unshared and SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

The need for this fast path optimization is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

October 22, 2006, at 10:48 AM by 67.169.17.159 -
Changed line 5 from:

This is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

to:

The need for this fast path optimization is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

October 22, 2006, at 10:48 AM by 67.169.17.159 -
Changed lines 3-4 from:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

to:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

October 22, 2006, at 10:48 AM by 67.169.17.159 -
Changed lines 3-4 from:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

to:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

October 22, 2006, at 10:47 AM by 67.169.17.159 -
Changed lines 3-4 from:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

to:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within SharedMemoryByteSlice's dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

October 22, 2006, at 10:47 AM by 67.169.17.159 -
Changed lines 3-4 from:

SharedMemoryByteSlice increments and decrements its SharedData "userCount." A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

to:

SharedMemoryByteSlice increments and decrements its SharedData "userCount" to indicate its reference to the SharedData. A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

October 22, 2006, at 10:47 AM by 67.169.17.159 -
Changed lines 3-5 from:

SharedMemoryByteSlice increments and decrements its SharedData "userCount." A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects. This is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

to:

SharedMemoryByteSlice increments and decrements its SharedData "userCount." A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects.

This is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

October 22, 2006, at 10:47 AM by 67.169.17.159 -
Changed lines 1-3 from:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the data is considered unshared and SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

to:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the data is considered unshared and SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

SharedMemoryByteSlice increments and decrements its SharedData "userCount." A userCount of 1 allows for an important "fast path" optimization which prevents cluttering the MyDocument's TavlTreeByteArray with additional ByteArrayPieces. The decrement of the userCount occurs within the dealloc method. Therefore, deterministic deallocation of SharedMemoryByteSlices is very important; take great care when autoreleaseing these objects. This is the principal barrier to supporting garbage collection within Hex Fiend, when Mac OS X supports that for Cocoa.

October 22, 2006, at 10:06 AM by 67.169.17.159 -
Changed line 1 from:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

to:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the data is considered unshared and SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

October 22, 2006, at 10:05 AM by 67.169.17.159 -
October 22, 2006, at 10:05 AM by 67.169.17.159 -
Changed line 1 from:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually.

to:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually. If the "userCount" of the shared data is 1, then the SharedMemoryByteSlice may modify that data directly. This is the principal mechanism by which simple modifications to the document's data, such as typing an additional character, do not require adding additional ByteArrayPieces to the ByteArray.

October 22, 2006, at 10:01 AM by 67.169.17.159 -
Added line 1:

SharedMemoryByteSlice is a concrete subclass of ByteSlice that references a SharedData. SharedMemoryByteSlice is used for data that the user types in manually.

Edit - History - Print - Recent Changes - Search
Page last modified on May 03, 2007, at 07:18 PM