Visual D 0.3.36 released - support for Alex Bothe's semantic analysis, LDC and profiling

Rainer Schuetze r.sagitario at gmx.de
Sat Jun 1 08:10:27 PDT 2013



On 01.06.2013 16:59, Flamaros wrote:
> On Saturday, 1 June 2013 at 10:55:36 UTC, Rainer Schuetze wrote:
>>
>>
>> On 01.06.2013 12:45, Flamaros wrote:
>>> On Thursday, 30 May 2013 at 22:39:28 UTC, Flamaros wrote:
>>
>>> I followed indications, lst files are correctly generated for the code
>>> coverage, but I don't have the coloration in the editor. Can be because
>>> my application crash when exiting?
>>
>> If your application crashed, the lst file might be from a previous run
>> and is considered out of sync. Please check whether it is newer than
>> the source file.
>> Also, it has to be in the same folder with the same base name as the
>> source. I've recently noticed that the lst files generation seem to
>> replace '/' with '-' in path names making it pretty unpredictable were
>> to look for files when all you know the source file name. I'll have to
>> add a workaround for that.
>
> When I check last modification of lst files it seems good.
>
> Effectively files name contains '-' characters (ex :
> "..-src-dquick-item-mouseAreaItem.lst")
> Source file naming prevent '-' characters, so if everybody follow this
> rule replacing '-' by '/' will allow you to get right paths.

I guess Visual D will have to remember the last directory where it 
invoked the "Compile and Run" command and try to match lst files in that 
directory to the current source file.

Does anybody know why the lst file is not written side-by-side with the 
source file?


More information about the Digitalmars-d-announce mailing list