thisExePath "returns the full path of the current executable".

If I run something like "./mysource.d" (using rdmd shebang) it returns the full path to compiled executable in /tmp folder (not so useful I think!). Is there a way to have the path of source itself?

On 2014-01-17 10:23, Andrea Fontana wrote:
> thisExePath "returns the full path of the current executable".
>
> If I run something like "./mysource.d" (using rdmd shebang) it returns
> the full path to compiled executable in /tmp folder (not so useful I
> think!). Is there a way to have the path of source itself?

That doesn't sound very easy to fix. When running the executable it's completely disconnected from the source file it was compiled from. Except for possibly some debug info.

-- 
/Jacob Carlborg

Hmm I thought It can be done reading __FILE__ at compile-time, but it gives me just the relative path.

Recent topic here: http://forum.dlang.org/thread/meuyppazxkrjcbgmkonl@forum.dlang.org


On Friday, 17 January 2014 at 09:29:48 UTC, Jacob Carlborg wrote:
> On 2014-01-17 10:23, Andrea Fontana wrote:
>> thisExePath "returns the full path of the current executable".
>>
>> If I run something like "./mysource.d" (using rdmd shebang) it returns
>> the full path to compiled executable in /tmp folder (not so useful I
>> think!). Is there a way to have the path of source itself?
>
> That doesn't sound very easy to fix. When running the executable it's completely disconnected from the source file it was compiled from. Except for possibly some debug info.

On 2014-01-17 10:50, Andrea Fontana wrote:
> Hmm I thought It can be done reading __FILE__ at compile-time, but it
> gives me just the relative path.

Right, forgot about __FILE__.

-- 
/Jacob Carlborg

On Friday, 17 January 2014 at 10:48:33 UTC, Jacob Carlborg wrote:
> On 2014-01-17 10:50, Andrea Fontana wrote:
>> Hmm I thought It can be done reading __FILE__ at compile-time, but it
>> gives me just the relative path.
>
> Right, forgot about __FILE__.

I think it would be useful to put full path on __FILE__ or to add another constant. Anyone?

On 2014-01-17 15:29, Andrea Fontana wrote:

> I think it would be useful to put full path on __FILE__ or to add
> another constant. Anyone?

I agree. Probably safest to add a new constant, to avoid breaking code.

-- 
/Jacob Carlborg