It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.

   Does Walter consider that worth of his attention to bother about?

Arlen Albert Keshabyan escribió:
>    It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.

Are you sure Eclipse does that to Java source files? I think Eclipse developed a Java compiler, from which they gather all that information.

> 
>    Does Walter consider that worth of his attention to bother about?
> 

Arlen Albert Keshabyan wrote:
>    It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.
> 
>    Does Walter consider that worth of his attention to bother about?

The problem is, it's difficult to determine exactly what should be in such a file. If you need complete semantic information, it would be a lot easier to just embed the DMD front-end or dil or something.

Robert Fraser Wrote:

> Arlen Albert Keshabyan wrote:
> >    It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.
> > 
> >    Does Walter consider that worth of his attention to bother about?
> 
> The problem is, it's difficult to determine exactly what should be in such a file. If you need complete semantic information, it would be a lot easier to just embed the DMD front-end or dil or something.

what are you talking about? :) Of course, it's not difficult to a compiler :) whatever documented file format would provide is sufficient for this! "What should be in such a file" is the matter of what Wllter considers to be possible to provide :) Whatever is valuable! Even a minute speckle of dust that helps :) None but compiler can provide the best info on what the source code is :)

Arlen Albert Keshabyan wrote:
> Robert Fraser Wrote:
> 
>> Arlen Albert Keshabyan wrote:
>>>    It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.
>>>
>>>    Does Walter consider that worth of his attention to bother about?
>> The problem is, it's difficult to determine exactly what should be in such a file. If you need complete semantic information, it would be a lot easier to just embed the DMD front-end or dil or something.
> 
> what are you talking about? :) Of course, it's not difficult to a compiler :) whatever documented file format would provide is sufficient for this! "What should be in such a file" is the matter of what Wllter considers to be possible to provide :) Whatever is valuable! Even a minute speckle of dust that helps :) None but compiler can provide the best info on what the source code is :)

I meant easier for Walter. A great deal of semantic info is produced if you run dmd with the -v switch, but going as deep as you suggest is quite a bit of work.

Robert Fraser Wrote:

> Arlen Albert Keshabyan wrote:
> > Robert Fraser Wrote:
> > 
> >> Arlen Albert Keshabyan wrote:
> >>>    It would be very handy to introduce a special compilation mode in the D compiler that would build a special report file instead of a binary object file upon a source code file compilation. It’s supposed to contain special information on types, variable and class names, errors, warnings, optimization notes and other useful information that would help an IDE (or any other frontends) to help programmers in a code completion and in other useful things. It’s supposed to run fast in a background like Eclipse does that to java source files.
> >>>
> >>>    Does Walter consider that worth of his attention to bother about?
> >> The problem is, it's difficult to determine exactly what should be in such a file. If you need complete semantic information, it would be a lot easier to just embed the DMD front-end or dil or something.
> > 
> > what are you talking about? :) Of course, it's not difficult to a compiler :) whatever documented file format would provide is sufficient for this! "What should be in such a file" is the matter of what Wllter considers to be possible to provide :) Whatever is valuable! Even a minute speckle of dust that helps :) None but compiler can provide the best info on what the source code is :)
> 
> I meant easier for Walter. A great deal of semantic info is produced if you run dmd with the -v switch, but going as deep as you suggest is quite a bit of work.

Right. So, that was the question.