You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great (and reasonably straight forward) to have an action available when right-clicking on a *.c file that prompts the user for a destination output (defaulting to same file name but with .di extension in same directory) then attempts to use dmd based on the syntax above.
Without dmd (or potentially ldc) configured the option should be visible in the context menu but not enabled.
This is currently dmd (ldc should work soon) only! There is an issue running this with gdc
There will need to be a good level of error handling and the terminal output should probably be made visible to the user.
The text was updated successfully, but these errors were encountered:
In saying that, this probably won't do what you want it to. You'd be missing any include paths ext. and for Windows we still haven't solved the whole needing the VS vars to be loaded in.
Basically, fully self-contained files might work, but that's about it.
understood. it'll be limited but I think it's worth getting some initial support in for this feature and work through pitfalls over time. Managing user expectations will be important so the UI will need to indicate limitations somehow.
Yes, it's a happy accident that it works even in the simplest of cases. The main thing here is that us going into it must keep it described as limited. Otherwise, people are gonna be unhappy!
As discussed in this forum thread https://forum.dlang.org/post/ugvc3o$5t3$1@digitalmars.com, dmd can generate di files (essentially D header files) from C code:
It would be great (and reasonably straight forward) to have an action available when right-clicking on a *.c file that prompts the user for a destination output (defaulting to same file name but with .di extension in same directory) then attempts to use dmd based on the syntax above.
The text was updated successfully, but these errors were encountered: