Which API?

The 1.3.3 beta seems to be going well – no news must be good news. I’ve been pondering over the host demos, specifically the Configuration Descriptor processing code, and I’ve made a few steps to improve the API.
I’ve come up with two shortlisted APIs for the next version. The first API is an extention of the current API, with new functions to search for the next descriptor of a given type after another given type, and for searching for descriptors of a given type before another given type.

The second API uses a plug-in comparator system. A generic “find next descriptor” routine takes a comparator function as an argument, which the uses supplies. The second method allows for much more flexibility, at the expense of a few bytes more of FLASH.

I’ve decided to get some feedback on which API should be included in the next library version. Head over to the thread on AVRFreaks, download the API samples and vote which one you think is the superior API.

 

Comments

No comments so far.

Leave a Reply

 
(will not be published)
 
 
Comment
 
 

 

Vital Stats

  • 35 Years Old
  • Australian
  • Lover of embedded systems
  • Firmware engineer
  • Self-Proclaimed Geek

Latest Blog Posts

RSS