THE FTS C PROGRAMMING STYLE GUIDE

ID# : 2261
Under Category : Tutorial Programming C
Source: www.literateprogramming.com

Cached Content

This are the official C programming guidelines for the FTS team. Why a . External objects programming in Max derive from times where ANSI C was still a .

File Summary

Why a style guide ? External objects programming in Max derive from times where ANSI C was still a dream, and "static" denotated aprogram that don't move too much. It is very likely, and already happened, that code written by external objects programmer will be included in officialMax/Fts distribution, and that the FTS team will be required to support this code. As the introduction of tabpeek and tabpoke proved, putting some code in a directory called "unsupported" don't prevent it to be widely used if the functionality implemented is needed in the user base. For this reason, no future release will include unsupported C code written in Ircam; if an object is included in theofficial Ircam distribution, it is fully supported by the development team. But adding source code to support to a system already difficult to maintain raises the maintenance cost, and ourresources are limited. In order to reduce this cost, we require that any contribution under the form of C source code have to comply withthe following guidelines in order to included in an official distribution. In general, if your C source do not fully comply with the the guidelines will *not* be accepted, under any condition;for some of the point we use the term "recommended"; this means that we may decide to accept some source C alsoif they don't comply with some of the recommended guidelines.

             Help others by telling us that this link is not pdf file.