On 2011-04-24 01:39, Jonathan M Davis wrote:
On 2011-04-22 01:54, Jonathan M Davis wrote:
Jonathan M Davis wrote:
I just checked. Exception _does_ take a default file and line number.
Huh, maybe my dmd is getting old.
Maybe we should revisit this after the next dmd release. Sounds like
one i
> On 2011-04-22 01:54, Jonathan M Davis wrote:
> >> Jonathan M Davis wrote:
> >>> I just checked. Exception _does_ take a default file and line number.
> >>
> >> Huh, maybe my dmd is getting old.
> >>
> >> Maybe we should revisit this after the next dmd release. Sounds like
> >> one is coming pre
On 2011-04-22 01:54, Jonathan M Davis wrote:
Jonathan M Davis wrote:
I just checked. Exception _does_ take a default file and line number.
Huh, maybe my dmd is getting old.
Maybe we should revisit this after the next dmd release. Sounds like
one is coming pretty soon with a lot of yummy goodn
On 04/22/2011 03:53 AM, Robert Jacques wrote:
On Thu, 21 Apr 2011 18:24:55 -0400, Adam D. Ruppe
wrote:
[snip]
Or, there's a whole new approach:
e) Duck typing for ranges in to!() might be a bad idea. Again, remember,
a class might legitimately offer a range interface, so it would
trigger this
On 04/22/2011 01:25 AM, Adam D. Ruppe wrote:
bearophile wrote:
Maybe exceptions nature should be changed a little so they store
__FILE__ and __LINE__ on default (exceptions without this
information are kept on request, for optimization purposes).
I'd like that. Even with a stack trace, it's
On 04/22/2011 12:24 AM, Adam D. Ruppe wrote:
I just made an innocent little change to one of my programs, hit
compile, and got this vomit:
/home/me/d/dmd2/linux/bin/../../src/phobos/std/conv.d(97): Error: template
std.conv.toImpl(T,S) if (!implicitlyConverts!(S,
T)&& isSomeString!(T)&& isInput
On Thu, 21 Apr 2011 18:24:55 -0400, Adam D. Ruppe
wrote:
[snip]
Or, there's a whole new approach:
e) Duck typing for ranges in to!() might be a bad idea. Again, remember,
a class might legitimately offer a range interface, so it would
trigger this message without opDispatch.
If ranges are me
Jonathan M Davis wrote:
> It was in dmd 2.052.
This is almost definitely my error then... I still have 2.050!
I didn't realize so much has passed since my last update :S
On 4/22/11, Sean Kelly wrote:
> On Apr 21, 2011, at 4:10 PM, Andrej Mitrovic wrote:
>
>> Btw, there is a stack trace for Windows and D2, see here:
>> http://3d.benjamin-thaut.de/?p=15
>
> Already in the next DMD release.
>
Whoa, the next release is gonna be big.
> Jonathan M Davis wrote:
> > I just checked. Exception _does_ take a default file and line number.
>
> Huh, maybe my dmd is getting old.
>
> Maybe we should revisit this after the next dmd release. Sounds like
> one is coming pretty soon with a lot of yummy goodness in it. All
> of this Exceptio
> Jonathan M Davis wrote:
> > It _does_ generally make sense for the file and line number to be
> > from the throw point rather than the point where you called the
> > function (especially when the throw point could be several function
> > calls away in the stack), but without a proper stack trace,
Jonathan M Davis wrote:
> I just checked. Exception _does_ take a default file and line number.
Huh, maybe my dmd is getting old.
Maybe we should revisit this after the next dmd release. Sounds like
one is coming pretty soon with a lot of yummy goodness in it. All
of this Exception stuff may be m
Jonathan M Davis wrote:
> It _does_ generally make sense for the file and line number to be
> from the throw point rather than the point where you called the
> function (especially when the throw point could be several function
> calls away in the stack), but without a proper stack trace, you
> hav
On Apr 21, 2011, at 4:10 PM, Andrej Mitrovic wrote:
> Btw, there is a stack trace for Windows and D2, see here:
> http://3d.benjamin-thaut.de/?p=15
Already in the next DMD release.
> bearophile wrote:
> > Maybe exceptions nature should be changed a little so they store
> >
> > __FILE__ and __LINE__ on default (exceptions without this
> > information are kept on request, for optimization purposes).
>
> I'd like that. Even with a stack trace, it's nice to have that
> availabl
bearophile wrote:
> Maybe exceptions nature should be changed a little so they store
> __FILE__ and __LINE__ on default (exceptions without this
> information are kept on request, for optimization purposes).
I'd like that. Even with a stack trace, it's nice to have that
available right at the top
Btw, there is a stack trace for Windows and D2, see here:
http://3d.benjamin-thaut.de/?p=15
> This is a more general problem of runtime errors, not just of to!(). Maybe
> exceptions nature should be changed a little so they store __FILE__ and
> __LINE__ on default (exceptions without this information are kept on
> request, for optimization purposes).
Vote up for that. At least it should
> Adam D. Ruppe:
> > c) Maybe Phobos could help out somehow? Another thing to!()
> > annoys the living crap of me with is it's runtime errors. It, again,
> > doesn't tell me where in my code the problem occurred.
> >
> > Perhaps have it take default __FILE__ and __LINE__ args to print out
> > too?
Adam D. Ruppe:
> c) Maybe Phobos could help out somehow? Another thing to!()
> annoys the living crap of me with is it's runtime errors. It, again,
> doesn't tell me where in my code the problem occurred.
>
> Perhaps have it take default __FILE__ and __LINE__ args to print out
> too? I think this
I just made an innocent little change to one of my programs, hit
compile, and got this vomit:
/home/me/d/dmd2/linux/bin/../../src/phobos/std/conv.d(97): Error: template
std.conv.toImpl(T,S) if (!implicitlyConverts!(S,
T) && isSomeString!(T) && isInputRange!(Unqual!(S)) &&
isSomeChar!(ElementType!(
21 matches
Mail list logo
