On Thu, 2011-06-09 at 17:48 +0200, Antonio Ospite wrote: > On Thu, 9 Jun 2011 11:30:56 -0400 > Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx> wrote: > > > Hi, > > > > On Thu, Jun 9, 2011 at 9:57 AM, Antonio Ospite <ospite@xxxxxxxxxxxxxxxxx> wrote: > > > Would you mind if I keep these three stdlib ones in? I use this code > > > verbatim in another program which does not link against Glib. > > > > But you use e.g. "g_strcmp0()", GIOChannel etc. How is that? > > > > Also remember sed is your friend :) > > > > I was referring to the "low level" functions: > get_feature_report() > set_feature_report() > get_device_bdaddr() > set_master_bdaddr() > > sorry, I use them in a command line tool which opens the hidraw node > directly without udev. > > But as you say, it is not a big deal to substitute them, if you like a > more uniform style in the bluez plugin then I'll comply. If it makes it easier for testing, split them out in a separate file, add a header, and a test program in bluez directly. That'll stop the 2 copies getting out of sync. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
