on 3/22/05 5:49 AM, Alfred Van Hoek at vanhoek at mac dot com wrote:
> However, it seems that calling REALNewMemoryBlock(0) would result in a nil
> pointer, contrary to calling memblock = new memBlock(0) in Realbasic?
>
> So how should I address these potential caveats?
Setting the size to 0 when a REALmemoryBlock with size is 4 was created
fails (remains at 4), however, setting the size to 1 does not fail. This is
not very helpful. REALNewMemoryBlock(0) results in a nil pointer, so it is
impossible to create a REALmemoryBlock with size equal to zero.
This seems to contradict the notion that an empty REALstring can be
instantiated.
Is the above a bug or a feature?
Alfred
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|