In compiler technology, ‘object code’ refers to the code generated by a compiler, containing the same semantical information as the ’source code’ that has been compiled, but in a form better suited for the task at hand. Quite often, the goal is execution by a physical or virtual processor.
This term was coined decades back, long long before the object orientation was invented in Sweden by the Simula-67 team (the class concept, grouping data and the operations that work on them), though… Hey, that was 51 years ago! From this point of view, the Scheme data structures built by the LilyPond compiler are a form of object code: the semantical contents is the same hopefully as that of the LilyPond code, and it’s better suited to the production of nice scores. JM > Le 18 avr. 2018 à 17:22, Carl Sorensen <[email protected]> a écrit : > > > > On 4/18/18, 6:51 AM, "Robert Hickman" <[email protected]> wrote: > > If lilypond is based on a functional interface, the documentation > making extensive use of the terms 'object' and 'interface' is > confusing. > > Patches to documentation will be reviewed. > http://lilypond.org/doc/v2.19/Documentation/contributor/documentation-work > > Carl > > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
