On Wednesday, 29 May 2019 at 16:08:11 UTC, Exil wrote:
On Wednesday, 29 May 2019 at 08:45:45 UTC, Andre Pany wrote:
[...]
I imagine __FILE__ is used where the code is defined, since it
is defined in "a.d" that is what is used. If you want to know
the file name of where it is used then you
On Wednesday, 29 May 2019 at 08:45:45 UTC, Andre Pany wrote:
Hi,
I have a module a.d
---
struct TestClass
{
string name;
string fileName;
}
TestClass[] testClasses;
mixin template UnitTest()
{
private static string getFileName(string fileName =
__FILE__)
{
Hi,
I have a module a.d
---
struct TestClass
{
string name;
string fileName;
}
TestClass[] testClasses;
mixin template UnitTest()
{
private static string getFileName(string fileName = __FILE__)
{
return fileName;
}
private static this()
{
On Wednesday, 22 June 2016 at 17:52:26 UTC, Ali Çehreli wrote:
On 06/22/2016 10:07 AM, Andre Pany wrote:
> Hi,
>
> I thought a mixin template is copied into the place where the
mixin
> statement
> exists and then the coding is evaluated.
> This seems not to be true for __FILE__
Apparently its
On 06/22/2016 10:07 AM, Andre Pany wrote:
> Hi,
>
> I thought a mixin template is copied into the place where the mixin
> statement
> exists and then the coding is evaluated.
> This seems not to be true for __FILE__
Apparently its the whole template that supports that. Is moving the
'file'
Hi,
I thought a mixin template is copied into the place where the
mixin statement
exists and then the coding is evaluated.
This seems not to be true for __FILE__
I have a module form, which has a class Form. This module also
contains
following mixin template
mixin template formTemplate()
{
