
|
[openbeosnetteam]
||
[Date Prev]
[08-2004 Date Index]
[Date Next]
||
[Thread Prev]
[08-2004 Thread Index]
[Thread Next]
[openbeosnetteam] Re: DHCP Status
- From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Wed, 25 Aug 2004 17:38:12 +0200
Hi David, nice to hear from you!
David wrote:
> Writing this pseudo-code reminds me of something else. I figure I
> should convert my functions to using BString sometime. It would make
> coding easier, but should I? Where this code will be integrated, will
> it be able to use the BString object? For my own coding, can I link to
> a library containing the BString object without having to go through all
> the trouble of downloading and compiling lots of Haiku?
We have BMallocIO which automatically manages memory for you. It should be
better-suited for binary data than BString (I don't know if you planned to
write binary data to the buffer).
Axel wrote:
> Yes, we have the driver_settings implementation; it can be used by
> config files easily.
> It will be in our libroot.so (maybe slightly changed), so you can use
> it now by directly linking driver_settings.o into your executable (or
> compile the source with yours - there are a lot of examples in the
> repository how you would do this with Jam, especially the test section
> is full with these, there is even a test for that API as well).
And you might want to look at my settings_tools.cpp/h in the libkernelppp
source (network/ppp/shared). It contains many useful functions for handling
driver_parameter structures, but do not use functions that make changes to the
driver_settings/parameter structure(s). Those should only be used with the
structures returned by dup_driver_settings() and new_driver_xxx().
Bye,
Waldemar
|

|