<html>
<head>
<base href="http://bugzilla.gdcproject.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - gdc segfault on scope(failure)"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=165#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - gdc segfault on scope(failure)"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=165">bug 165</a>
from <span class="vcard"><a class="email" href="mailto:ketmar@ketmar.no-ip.org" title="Ketmar Dark <ketmar@ketmar.no-ip.org>"> <span class="fn">Ketmar Dark</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=79&action=diff" name="attach_79" title="hackfix for 'aliased import' segfault">attachment 79</a> <a href="attachment.cgi?id=79&action=edit" title="hackfix for 'aliased import' segfault">[details]</a></span>
hackfix for 'aliased import' segfault
aaaah, got it! it's caused by double call to ImportStatement::semantic().
current DMD checks if there was only one call (with assertion), but i'm too
lazy to track this to other places (i suspect there are alot of such 'double
calls' scattered across 2.065 codebase anyway), so i just added a simple hack
that bails out of analyser if it sees that something was already done.
don't know if it will cause any problems for you, but for me it at least allows
to build my project successfully (and the project actually works).
not sure if it worth a "proper" fix anyway, as 2.065 codebase is soon ;-) to be
replaced.
side note: seems that not so many people does aliased imports is scope guards.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>