Possible bug in boxing unit?
jcc7
jcc7_member at pathlink.com
Wed May 17 09:47:44 PDT 2006
In article <e4fisl$43r$1 at digitaldaemon.com>, akcom says...
>
>H:\workspace\server>dmd -unittest -v main.d settings.d
>parse main
>parse settings
>semantic main
>semantic settings
>semantic2 main
>semantic2 settings
>semantic3 main
>semantic3 settings
>code main
>generating code for function 'main'
>code settings
>generating code for function 'this'
>generating code for function 'this'
>generating code for function '_dtor'
>generating code for function 'set'
>generating code for function 'unset'
>generating code for function 'get'
>generating code for function 'isSet'
>generating code for function 'keyList'
>generating code for function '__unittest0'
>generating code for function 'unboxable'
>generating code for function 'unboxCastInteger'
>E:\dmd\bin\..\..\dm\bin\link.exe main+settings,,,user32+kernel32/noi;
>OPTLINK (R) for Win32 Release 7.50B1
>Copyright (C) Digital Mars 1989 - 2001 All Rights Reserved
>
>settings.obj(settings)
> Error 42: Symbol Undefined _assert_3std5boxer
>--- errorlevel 1
Looks you've stumbled upon std.boxer's "Release Mode Bug".
http://www.prowiki.org/wiki4d/wiki.cgi?DocComments/Phobos/StdBoxer
It's already in BugZilla, too:
http://d.puremagic.com/bugzilla/show_bug.cgi?id=8
jcc7
More information about the Digitalmars-d-bugs
mailing list