On Tuesday, 3 March 2015 at 17:49:07 UTC, Benjamin Thaut wrote:
Any suggestions how to fix this issue? I'm also open for
implementation hints.
Kind Regards
Benjamin Thaut
Running unittests that access private symbols from the other side
of the dll boundary sounds like a very hard problem to
On Thursday, 5 March 2015 at 07:28:12 UTC, Jacob Carlborg wrote:
On 2015-03-03 18:49, Benjamin Thaut wrote:
Sounds like you want to test an application that uses Phobos as
a DLL. To me that sounds like a more higher level test than a
unit test, i.e. integration tests. I would put those tests
On Thursday, 5 March 2015 at 03:24:05 UTC, TheFlyingFiddle wrote:
Finding out if a unittest only accesses public symbols could be
done by analyzing the ast of the method. Either inside the
compiler of via one of the third party D parsers currently in
use.
I thought about writing a tool
On 2015-03-05 08:38, Benjamin Thaut wrote:
I don't want to write new tests. I want to use the tests for phobos
which are already there. And I want to use them in a way, that if new
tests are added to phobos they are also tested against the dll version
of phobos. Yes integration tests would be
On 2015-03-03 18:49, Benjamin Thaut wrote:
I'm currently in the process of annotating all of phobos with export
and its quite cumbersome. To verify that I annoted all relevant
functions and types with export I would like to run the unitests against
the shared version of phobos. There is a
On Thursday, 5 March 2015 at 07:42:10 UTC, Jacob Carlborg wrote:
On 2015-03-05 08:38, Benjamin Thaut wrote:
I don't want to write new tests. I want to use the tests for
phobos
which are already there. And I want to use them in a way, that
if new
tests are added to phobos they are also tested
I'm currently in the process of annotating all of phobos with export
and its quite cumbersome. To verify that I annoted all relevant
functions and types with export I would like to run the unitests against
the shared version of phobos. There is a problem with this though. The
unittests are
