"J C Calvarese" <jcc7@cox.net> wrote in message news:cnjocm$t1r$1@digitaldaemon.com...
> I think Phobos is good.  I just think there needs to be more in it (which will likely improve over time). We have to start somewhere, so I don't mean to whine about Phobos's completeness.

Lots of people have written various parts for Phobos. If you find that you need a module xyz for a project, and it would be of general value, by all means!

"Lynn Allan" <l_d_allan@adelphia.net> wrote in message news:cnjfds$h6s$1@digitaldaemon.com...
> "Walter" <newshound@digitalmars.com> wrote in message news:cng0lv$1fmq$1@digitaldaemon.com...
> > > * debugging has improved, but has a ways to go
> > In what way?
>
> As of dmd 0.105, I find it difficult to debug char[] (aka strings)
> I've been using a Visual Studio 98 workaround from (I think?) "Arcane
> Jill" (thx ... who has been mia lately?)
>
> #  char[] myVar = "Local Variable";  // Visible indirectly
> #               // len is (int)myVar
> #               // char is (char*)((int)(myVar >>32))
> #  char* p = "Pointer";              // Visible to debugger
> #  debug char* _dbgMyVar = myVar;  // Visible to debugger

I understand the problem. I had it showing up in the debugger as a 'struct' with two fields, a length and a pointer. (This is because C debuggers have no conception of D strings!) The trouble started because the debugger assumes different calling conventions for longlongs and structs. Arrggh. I was forced to abandon that. There isn't much to be done outside of wheedling the debugger makers to support the D string type.

'D' is so good that the 'loose ends' are that much more noticeable.

Keep up the good work!

On Thu, 18 Nov 2004 19:32:34 -0800, Walter <newshound@digitalmars.com> wrote:

>
> "Lynn Allan" <l_d_allan@adelphia.net> wrote in message
> news:cnjfds$h6s$1@digitaldaemon.com...
>> "Walter" <newshound@digitalmars.com> wrote in message
>> news:cng0lv$1fmq$1@digitaldaemon.com...
>> > > * debugging has improved, but has a ways to go
>> > In what way?
>>
>> As of dmd 0.105, I find it difficult to debug char[] (aka strings)
>> I've been using a Visual Studio 98 workaround from (I think?) "Arcane
>> Jill" (thx ... who has been mia lately?)
>>
>> #  char[] myVar = "Local Variable";  // Visible indirectly
>> #               // len is (int)myVar
>> #               // char is (char*)((int)(myVar >>32))
>> #  char* p = "Pointer";              // Visible to debugger
>> #  debug char* _dbgMyVar = myVar;  // Visible to debugger
>
> I understand the problem. I had it showing up in the debugger as a 'struct'
> with two fields, a length and a pointer. (This is because C debuggers have
> no conception of D strings!) The trouble started because the debugger
> assumes different calling conventions for longlongs and structs. Arrggh. I
> was forced to abandon that. There isn't much to be done outside of wheedling
> the debugger makers to support the D string type.
>
>

Since I'm using windbg (as you command :D) I managed to get some
help out of
*(char**)((@ebp - 0x8) + 0x4)
as a watch. Is it going to be possible to get .pdb files for poor
old confused windows? ;) (or is it already?)
I dont know much about calling conventions, though.

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

"Lynn Allan" <l_d_allan@adelphia.net> wrote in message news:cnk6qm$1hhe$1@digitaldaemon.com...
> 'D' is so good that the 'loose ends' are that much more noticeable.
>
> Keep up the good work!

No worrys there, I'm very committed to this.