View mode: basic / threaded / horizontal-split · Log in · Help
May 06, 2008
Re: "D" annoyances
"Tower Ty" <towerty@msn.com.au> wrote in message 
news:fvovbu$18gg$1@digitalmars.com...

> Yep its a runtime error . I should have said . As you can't file a bug 
> report without joining something and giving out emails I am using this as 
> a bug report venue and have been for some time .

Then you'll have to get used to people ignoring your bug reports.  Tango is 
maintained by a core team of about 3 people, all of whom have real lives and 
real jobs.  They just don't have the time or manpower to collate bug reports 
from all over the web.

Also, this is a runtime error.  Try throwing _any_ exception and you'll 
notice that no file or line is given.  In order to know where an exception 
occurred, either the language has to have some kind of built-in support 
whereby it will pass the file and line of the 'throw' statement to the 
exception's constructor (which it doesn't), or you have to have a traceback 
mechanism (which, by default, does not exist).  Apparently you can get 
traced exceptions in Tango by using flectioned; I've never used it.
May 06, 2008
Re: "D" annoyances
Jarrett Billingsley escreveu:
> "Tower Ty" <towerty@msn.com.au> wrote in message 
> news:fvovbu$18gg$1@digitalmars.com...
> 
>> Yep its a runtime error . I should have said . As you can't file a bug 
>> report without joining something and giving out emails I am using this as 
>> a bug report venue and have been for some time .
> 
> Then you'll have to get used to people ignoring your bug reports.  Tango is 
> maintained by a core team of about 3 people, all of whom have real lives and 
> real jobs.  They just don't have the time or manpower to collate bug reports 
> from all over the web.
> 
> Also, this is a runtime error.  Try throwing _any_ exception and you'll 
> notice that no file or line is given.  In order to know where an exception 
> occurred, either the language has to have some kind of built-in support 
> whereby it will pass the file and line of the 'throw' statement to the 
> exception's constructor (which it doesn't), or you have to have a traceback 
> mechanism (which, by default, does not exist).  Apparently you can get 
> traced exceptions in Tango by using flectioned; I've never used it. 
> 
> 

Or use ddbg (a debugger for d) and unwind the stack when the exception 
is thrown
May 06, 2008
Re: "D" annoyances
"Tower Ty" wrote
> BCS Wrote:
>
>> Jarrett Billingsley wrote:
>> > "BCS" <BCS@pathlink.com> wrote in message
>> > news:fvnauf$2hii$1@digitalmars.com...
>> >
>> >
>> >>>" tango.core.Exception.IllegalArgumentException: Argument not valid "
>> >>>
>> >>>Surely you cold put a line number, or other reference so it means
>> >>>something?
>> >>
>> >>file a bug report.
>> >
>> >
>> > I'm not so sure.  That looks like a runtime error, not a compile time 
>> > error.
>> >
>> > If he's getting the error when he tries to compile something, maybe 
>> > it's an
>> > error in a build tool, but it certainly does not look like a compile 
>> > time
>> > error.
>> >
>> >
>>
>> OK then file a tango bug report/feature request.
>
> Yep its a runtime error . I should have said . As you can't file a bug 
> report without joining something and giving out emails I am using this as 
> a bug report venue and have been for some time .
>
> If no-one chooses to do anything about them too bad . There are stacks of 
> choices for me.
>

Even if you filed this as a bug report, it wouldn't be sufficient.  There is 
no way of reproducing, no way of knowing whether you are throwing this 
exception in your code, or using another library, etc.  More information 
about what you are doing is necessary.

I don't think any reasonable software development team is going to take a 
bug report seriously if you don't take it seriously.  If you would rather 
not use Tango, then that is a viable option.  If your goal is to use Tango, 
put in some effort and file a ticket.

Even digitalmars uses a bug reporting system, and their team pretty much 
doesn't do anything without a bug report there.  The newsgroup is for 
fleshing out ideas, seeing if someone else knows how to solve a problem, 
asking if a bug is already known, etc.  It is not a bug reporting mechanism.

-Steve
Next ›   Last »
1 2
Top | Discussion index | About this forum | D home