On 02/01/2018 08:07 AM, sc...@scottlinder.com wrote:
Hi John,
In the case where the files are actually available on disk, and the
source is simply being "cached", the attributes are exactly the same. In
the case where sources are generated, and so have no true path on disk,
I would suggest we
On 02/01/2018 12:01 PM, sc...@scottlinder.com wrote:
Hi Paul,
My intention was to support an empty source string; I want to be
explicit about the presence of embedded source for each file.
I'm not fond of the belt and suspenders approach. If there is one
specifier for an attribute, there's n
> -Original Message-
> From: sc...@scottlinder.com [mailto:sc...@scottlinder.com]
> Sent: Thursday, February 01, 2018 12:02 PM
> To: Robinson, Paul; dwarf-discuss@lists.dwarfstd.org
> Subject: RE: [Dwarf-Discuss] DWARF and source text embedding
>
> Hi Paul,
>
> My intention was to suppo
Hi Paul,
My intention was to support an empty source string; I want to be
explicit about the presence of embedded source for each file.
When reading the spec I did notice places where an empty string can
indicate the absence of the attribute (e.g. DW_AT_name), but I would
prefer to be explic
> -Original Message-
> From: Dwarf-Discuss [mailto:dwarf-discuss-boun...@lists.dwarfstd.org] On
> Behalf Of sc...@scottlinder.com
> Sent: Wednesday, January 31, 2018 2:05 PM
> To: dwarf-discuss@lists.dwarfstd.org
> Subject: [Dwarf-Discuss] DWARF and source text embedding
>
> Hello all,
>
Hi John,
In the case where the files are actually available on disk, and the
source is simply being "cached", the attributes are exactly the same. In
the case where sources are generated, and so have no true path on disk,
I would suggest we might just leave the exact meaning to be
implementat
