I'm getting this with this code: http://dpaste.dzfl.pl/55f83be6
Can someone explain me, _why_ i get this error? o.O
I thought D cannot detect null references by itself.
On Monday, 2 July 2012 at 15:55:03 UTC, Namespace wrote:
I'm getting this with this code: http://dpaste.dzfl.pl/55f83be6
Can someone explain me, _why_ i get this error? o.O
I thought D cannot detect null references by itself.
Can't check now. But if you get this during runtime, D does
detect
On Monday, 2 July 2012 at 16:19:08 UTC, Tobias Pankrath wrote:
On Monday, 2 July 2012 at 15:55:03 UTC, Namespace wrote:
I'm getting this with this code: http://dpaste.dzfl.pl/55f83be6
Can someone explain me, _why_ i get this error? o.O
I thought D cannot detect null references by itself.
On Monday, July 02, 2012 17:55:01 Namespace wrote:
I'm getting this with this code: http://dpaste.dzfl.pl/55f83be6
Can someone explain me, _why_ i get this error? o.O
I thought D cannot detect null references by itself.
You didn't actually list what error you're seeing. The error that I'm
constructor.
- Jonathan M Davis
This code: http://dpaste.dzfl.pl/a0939681
prints
dmd -w -wi -O -property -unittest -debug -ofnot_null
not_null.d (im Verzeichnis: D:\D\D_Scripts\Test3)
not_null.d(106): Error: null dereference in function _Dmain
not_null.d(103): Error: null dereference
: null dereference in function _Dmain
not_null.d(103): Error: null dereference in function _Dmain
Kompilierung fehlgeschlagen.
And even without
@disable
this(typeof(null));
I get the same errors.
Well, I'm getting
q.d(111): Error: no identifier for declarator t
q.d(111): Error: found
...@forum.dlang.org?page=3
and here, if you like to read my mother language ;)
http://blog.rswhite.de/archives/791
but with that
fixed I see
Error: null dereference in function _Dmain
q.d(103): Error: null dereference in function _Dmain
which refers to
test_not_null_foo(f1);
which is a very weird
On 07/02/2012 11:36 AM, Jonathan M Davis wrote:
By the way, it's pointless to compile with both -w and -wi. -wi makes
it so
that warnings are displayed without stopping compilation. -w makes it
so that
warnings are displayed and treated as errors (so they stop
compilation). Pick
one or
).
but with that
fixed I see
Error: null dereference in function _Dmain
q.d(103): Error: null dereference in function _Dmain
which refers to
test_not_null_foo(f1);
which is a very weird error. test_not_null_foo takes a
NotNull!Foo, not a Foo,
and f1 is a Foo, and you haven't defined
On 07/02/2012 11:36 AM, Jonathan M Davis wrote:
By the way, it's pointless to compile with both -w and -wi. -wi makes
it so
that warnings are displayed without stopping compilation. -w makes it
so that
warnings are displayed and treated as errors (so they stop
compilation). Pick
one or
On Monday, July 02, 2012 12:45:16 Ali Çehreli wrote:
On 07/02/2012 11:36 AM, Jonathan M Davis wrote:
By the way, it's pointless to compile with both -w and -wi. -wi makes
it so
that warnings are displayed without stopping compilation. -w makes it
so that
warnings are displayed and
If you want to play around with that, that's fine, but the
language is not
going to change, so please to post code which uses your
changes. If you start
making changes to the compiler, you can't really expect other
people to help
you figure out what's wrong with your code - especially since
At last a further Stack overflow, maybe you could explain me why.
It comes if i try to outsource the redundant code with a mixin
template like this:
[code]
mixin template TRef(T : Object) {
private:
NotNull!(T) _nn;
public:
@property
NotNull!(T) GetNN() {
13 matches
Mail list logo
