The developer should not have to relearn service-agnostic concepts as they move between client libraries. Service-agnostic concepts such as logging, HTTP communication, and error handling should be consistent.In cases of conflict, consistency within the language is the highest priority and consistency between all target languages is the lowest priority. Client libraries should be consistent within the language, consistent with the service and consistent between all target languages.We work with the ecosystem to improve it for all developers.We embrace the ecosystem with its strengths and its flaws.It should feel natural to a developer in the target language. The SDK should follow the general design guidelines and conventions for the target language.Productivity is achieved by adhering to the principles described below: Idiomatic ![]() Other qualities (such as completeness, extensibility, and performance) are important but secondary. The Azure SDK should be designed to enhance the productivity of developers connecting to Azure services. You do not have to write a client library for C if your service is not normally accessed from IoT devices. The C guidelines are for the benefit of client library designers targeting service applications written in C, primarily IoT devices. DRAFT: The C Language guidelines are in DRAFT status Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |