[Hamlib-developer] Musings on backend behavior

[Nate B. <n0...@ne...>]

Hi all.

I'm in an email mood tonight.  :)

As I've worked on the backend library for the FT-920 a number of the
warts and quirks of the radio are exposed through the frontend library
to the application.  Really, I think this is incorrect as Hamlib should
hide these things from the application.

So, what I would like to see in the API documentation is a description
of the expected behavior of the function at hand.  While this is often
obvious, some things are more subtle and I would like a more defined
target to work toward.

Thus I think a firm definition of the virtual radio Hamlib presents to
the application would be a big help to authors on each side of the
frontend.

Comments?  Ideas?

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto