Re: Identify included files

[antlists]

On 21/05/2020 14:36, David Kastrup wrote:
> antlists <address@hidden> writes:
>
> > On 21/05/2020 01:49, David Wright wrote:
> > > I don't understand your equivalence between .ily and .h files. The
> > > .ily file(s) can contain just as much code as the .ly file(s), whereas
> > > .h files don't contain any code at all (in the sense of producing
> > > executable code for the next stage.
> >
> > a) just like .h files, .ily files can't be passed directly to a
> > compiler for compilation.
> >
> > b) who says .h files don't produce executable code? They often contain
> > code, sometimes entire functions.
>
> The point of .h files is that they are intended to be included by more
> than one compilation unit resulting in an executable.

Which is exactly how I use .ily files ...
> As such, they are limited with regard to the code they can contain.
> They can contain
>
> a) inline function definitions: those can occur in multiple compilation
> units as long as they are identical.

You're describing the way I define variables that contain all my notes. 
You're also describing how I define the musical structure.

> b) static inline: do not even need to be identical, are per-unit.
> c) static data definitions, are per-unit.
> d) template function definitions

I redefine the header function - I've NEVER seen a header laid out the 
way lilypond does it, apart from parts produced by lilypond ...

Plus I have my own dynamics definition file that extends lilypond's ones
> I don't think that .ly/.ily is all that comparable here...
The way I use .ily files EXACTLY matches your definition of a .h file... 
how on earth do you use them?

Cheers,
Wol