1. EDB storage format
Rob,
Looking at the way that EDB stores euphoria objects, is there any
combination of bytes that can be guaranteed to *NEVER* occur at the
start of the byte-representation of an object?
--
MrTrick
-------------------------------------------------------------------------------------
magnae clunes mihi placent, nec possum de hac re mentiri.
2. Re: EDB storage format
Patrick Barnes wrote:
>
> Rob,
> Looking at the way that EDB stores euphoria objects, is there any
> combination of bytes that can be guaranteed to *NEVER* occur at the
> start of the byte-representation of an object?
> --
It seems to me that there would never be something like this to start off a
stored object:
{251,0,0,0,0}
because the 251 is the I4B flag indicating a 4-byte integer followed, but
4-bytes would never be needed to store 0 as bytes {0,0,0,0} so {251,0,0,0,0}
should never occur. Is that correct?
3. Re: EDB storage format
Sounds good, thank you...
On Wed, 24 Nov 2004 17:28:33 -0800, Andy Serpa <guest at rapideuphoria.com>
wrote:
>
> posted by: Andy Serpa <ac at onehorseshy.com>
>
> Patrick Barnes wrote:
> >
> > Rob,
> > Looking at the way that EDB stores euphoria objects, is there any
> > combination of bytes that can be guaranteed to *NEVER* occur at the
> > start of the byte-representation of an object?
> > --
>
> It seems to me that there would never be something like this to start off a
> stored object:
>
> {251,0,0,0,0}
>
> because the 251 is the I4B flag indicating a 4-byte integer followed, but
> 4-bytes would never be needed to store 0 as bytes {0,0,0,0} so {251,0,0,0,0}
> should never occur. Is that correct?
>
>
>
>
--
MrTrick
