On Sun, Aug 20, 2006 at 12:24:50AM +0200, Josh Jennings wrote: > >No just add 'intelToHost_XX()' or 'HostToIntel' functions for reading > >data, or writing data. > >Then a host sensitive reader would have these defined appropriately for > >the endianness of > >the host. > > This is definitely the way to go. I have written the intel_to_host > functionality. I will do as Eric proposed and write a sink and source > block which takes care of this, unless someone comes up with it first. > > >This is done all the time throughout the networking code. > > Obvious example. Should of thought of that first. ;-) > > >Obviously if the files are never going to be seen outside the particular > >host, it doesn't matter. > > This is also right, but I guess I came across it since I do not have a > method on my mac of acquiring source data. Therefore I looked at what > people had made available. Being able to share data across platforms > is definitely meaningful even if at this point in gnuradio it seems a > minor one since it seems most people using gnuradio use their own > methods of generating/acquiring signals. Da know, addressing > endianness could be taken for granted but it may bite back later. > > Thanks, > Josh
In the naming convention department, I'd probably call it little_endian_to_host_XX or something similar. For the standard networking conversions, see $ man byteorder Eric _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
