This record is written in a file that i want to re-read with a Ruby
script (just a toy example... to understand).
I've not found a "clean" way to unpack such a record...
My C compiler gives me a total sizeof of 48, so i use a
fd.sysread(48).unpack(A32dIC) to re-read. But that seems rather
'tricky' (i suppose we don't have always such a
information). Furthermore, the first element is completed with
garbage if the name field have less than 30 "useful" chars ("Doe",
for example).
I'm sure i'm missing something but i've not managed to find the right
way to do that.
there isn't really a "clean" way to do this, since you are doing something inherently un-clean.
However, to fix the string issue, a possible solution is:
This record is written in a file that i want to re-read with a Ruby
script (just a toy example... to understand).
I've not found a "clean" way to unpack such a record...
My C compiler gives me a total sizeof of 48, so i use a
fd.sysread(48).unpack(A32dIC) to re-read. But that seems rather
'tricky' (i suppose we don't have always such a
information). Furthermore, the first element is completed with
garbage if the name field have less than 30 "useful" chars ("Doe",
for example).
I'm sure i'm missing something but i've not managed to find the right
way to do that.
Any clue?
-- Eric Jacoboni, ne il y a 1443970729 secondes
This record is written in a file that i want to re-read with a Ruby
script (just a toy example... to understand).
I've not found a "clean" way to unpack such a record...
My C compiler gives me a total sizeof of 48, so i use a
fd.sysread(48).unpack(A32dIC) to re-read. But that seems rather
Your struct says char name[30] not 32...
'tricky' (i suppose we don't have always such a
information). Furthermore, the first element is completed with
garbage if the name field have less than 30 "useful" chars ("Doe",
for example).
Did you initialize the C struct correctly? You should zero out all of name.
···
On Feb 21, 2006, at 6:28 AM, Eric Jacoboni wrote:
I'm sure i'm missing something but i've not managed to find the right
way to do that.
--
Eric Hodel - drbrain@segment7.net - http://segment7.net
This implementation is HODEL-HASH-9600 compliant
I'm curious about binary protocol parsing in ruby and have scratched
around for some kind of BinaryReader-ish interface for strings. Seems
like you could solve this if you know that your struct is in a string
you could say:
str = fd.sysread(n)
name = str.read_str(30)
size = str.read_double
age = str.read_int
stuff = str.read_c
I was going to write a native extension to do this after I finish my
current Ruby/AIO extension project. Unless there is something that
does this already (maybe in a cleaner/more ruby-ish way?)
···
On 2/21/06, Logan Capaldo <logancapaldo@gmail.com> wrote:
On Feb 21, 2006, at 9:28 AM, Eric Jacoboni wrote:
> Hi,
>
> Say i've a C struct like that:
>
> typedef struct {
> char name[30];
> double size;
> int age;
> char stuff;
> } enreg_t;
>
> This record is written in a file that i want to re-read with a Ruby
> script (just a toy example... to understand).
>
> I've not found a "clean" way to unpack such a record...
>
> My C compiler gives me a total sizeof of 48, so i use a
> fd.sysread(48).unpack(A32dIC) to re-read. But that seems rather
> 'tricky' (i suppose we don't have always such a
> information). Furthermore, the first element is completed with
> garbage if the name field have less than 30 "useful" chars ("Doe",
> for example).
>
> I'm sure i'm missing something but i've not managed to find the right
> way to do that.
>
> Any clue?
> --
> Eric Jacoboni, ne il y a 1443970729 secondes
>
there isn't really a "clean" way to do this, since you are doing
something inherently un-clean.
However, to fix the string issue, a possible solution is:
This is pretty much exactly what unpack does anyway., except its one method that uses a format string. If you wanted a more stream oriented wrapper around this, you certainly could write one fairly easily.
ri String#unpack
···
On Feb 21, 2006, at 2:19 PM, Jacob Repp wrote:
I'm curious about binary protocol parsing in ruby and have scratched
around for some kind of BinaryReader-ish interface for strings. Seems
like you could solve this if you know that your struct is in a string
you could say:
str = fd.sysread(n)
name = str.read_str(30)
size = str.read_double
age = str.read_int
stuff = str.read_c
I was going to write a native extension to do this after I finish my
current Ruby/AIO extension project. Unless there is something that
does this already (maybe in a cleaner/more ruby-ish way?)
Yes, I've needed one of these too (read + write). My application was
handling a binary UDP protocol. String#unpack doesn't support some of
the bizarro data formating that this protocol seems to have, so I cooked
up ReadBuffer/WriteBuffer[1] classes with a few methods a bit like those
above.
On Wed, Feb 22, 2006 at 04:19:07AM +0900, Jacob Repp wrote:
I'm curious about binary protocol parsing in ruby and have scratched
around for some kind of BinaryReader-ish interface for strings. Seems
like you could solve this if you know that your struct is in a string
you could say:
str = fd.sysread(n)
name = str.read_str(30)
size = str.read_double
age = str.read_int
stuff = str.read_c
I was going to write a native extension to do this after I finish my
current Ruby/AIO extension project. Unless there is something that
does this already (maybe in a cleaner/more ruby-ish way?)