On 1 March 2013 17:37, bdsatish wrote:
> Thanks Iain! Frankly, I'm new to GDC, so I didn't understand your
> explanation, but anyways, I'll pull from Git and re-check on my PC.
>
> --Satish
>
One was caused by a change in the front-end having a knock-on effect in
gdc. The other caused by dead c
Thanks Iain! Frankly, I'm new to GDC, so I didn't understand your
explanation, but anyways, I'll pull from Git and re-check on my
PC.
--Satish
http://gdcproject.org/bugzilla/show_bug.cgi?id=24
Johannes Pfau changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://gdcproject.org/bugzilla/show_bug.cgi?id=35
Johannes Pfau changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://gdcproject.org/bugzilla/show_bug.cgi?id=36
Johannes Pfau changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On 28 February 2013 21:45, Iain Buclaw wrote:
>
> On Feb 28, 2013 6:55 PM, "bdsatish" wrote:
> >
> > Hi,
> >
> > Some warning messages are being "leaked" from GDC's source code into
> end-user's code. I think this shouldn't happen and hence, is a bug.
> >
> > ```
> > // example.d
> > import std.