Re: Correct line/column numbers in byte compiler messages [Was: GNU is looking for Google Summer of Code Projects]

[Stefan Monnier]

> properties", but from reading
> https://www.gnu.org/software/guile/manual/html_node/Source-Properties.html
> it seems that it might use something similar to your approach?

It seems that Guile does it along the lines of "fat cons cells"
according to their example:

    scheme@(guile-user)> (xxx)
    <unnamed port>:4:1: In procedure module-lookup:
    <unnamed port>:4:1: Unbound variable: xxx
    
    scheme@(guile-user)> xxx
    ERROR: In procedure module-lookup:
    ERROR: Unbound variable: xxx

where only the code with a cons-cell gets location information.
That's also what the earlier text says:

    The way that source properties are stored means that Guile cannot
    associate source properties with individual symbols, keywords,
    characters, booleans, or small integers.

Tho, IIUC it seems that rather than "fat cons cells" they may be using
a hash-table indexed with the object (cons-cells or otherwise).


        Stefan