[Issue 13334] [infoleak] DMD always places module paths in data segment

https://issues.dlang.org/show_bug.cgi?id=13334 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 13334] [infoleak] DMD always places module paths in data segment

https://issues.dlang.org/show_bug.cgi?id=13334 Walter Bright changed: What|Removed |Added Keywords||betterC

[Issue 13334] [infoleak] DMD always places module paths in data segment

https://issues.dlang.org/show_bug.cgi?id=13334 --- Comment #2 from Vladimir Panteleev thecybersha...@gmail.com --- (In reply to Vladimir Panteleev from comment #0) 1) Do not generate these helper functions or strings when -betterC is specified. This is now in:

[Issue 13334] New: [infoleak] DMD always places module paths in data segment

https://issues.dlang.org/show_bug.cgi?id=13334 Issue ID: 13334 Summary: [infoleak] DMD always places module paths in data segment Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 13334] [infoleak] DMD always places module paths in data segment

https://issues.dlang.org/show_bug.cgi?id=13334 --- Comment #1 from Vladimir Panteleev thecybersha...@gmail.com --- Correction. There are two separate issues here: 1. DMD leaks information about the source code in a way that can't be turned off with compiler switches. 2. DMD emits information

Re: Module Paths

On Friday, 10 August 2012 at 02:20:18 UTC, Matt wrote: Is it possible to retrieve the file path to a module from within the module itself? Or, if not, are there any methods to retrieve the import location list (the argument -I that is passed to the compiler) from within code? I don't know of

Re: Module Paths

I'd like to try to track the source files, to watch for editing. The goal is for Run-time compiling, akin to runtime compiled C++, which allows the programmer to edit their modules, save them, then the program notices the change of file and recompiles, all while the program is still running.

Re: Module Paths

On 2012-08-10 14:06, Matt wrote: I'd like to try to track the source files, to watch for editing. The goal is for Run-time compiling, akin to runtime compiled C++, which allows the programmer to edit their modules, save them, then the program notices the change of file and recompiles, all while

Re: Module Paths

On Friday, 10 August 2012 at 13:44:13 UTC, Jacob Carlborg wrote: On 2012-08-10 14:06, Matt wrote: I'd like to try to track the source files, to watch for editing. The goal is for Run-time compiling, akin to runtime compiled C++, which allows the programmer to edit their modules, save them,

Module Paths

Is it possible to retrieve the file path to a module from within the module itself? Or, if not, are there any methods to retrieve the import location list (the argument -I that is passed to the compiler) from within code?