While doing screenshots for the gtkDcoding blog (See? I'm working
on it.) I discovered something cool about signal callback chains
in GtkD. So, I ended up rewriting the code and the blog post to
include this coolness.
You can read it here:
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()
{
change gwlib buildtype to sourceLibrary solves the problem, but
it should work for static or shared library.
