Learning asynchronous sockets in D (well actually C...)

[Tobias Pankrath]

> * add -g and -debug=splat (or any other keywords) to the build 
> command


You don't need a keyword -debug is sufficient. To make the binary 
work with a debugger you does not even need -debug, only -g. 
-debug only includes code that's in a debug-block.

> * gdb bin/SimpleServer
> * continue (on breakpoints)
> * run (to run the program)
> * bt (for backtrace)
>
> But of course, you all knew this before. But for a new D 
> developer that has never done anything in C or C++ this was 
> difficult as horses arse to understand.
>
> Is it wrong to badge myself with asynchronous sockets? :)
>
> https://github.com/jarlah/d2-simple-socket-server

I conclude from this, that you don't have any (much) experience 
with a unix c toolchain. May I ask what languages you come from? 
What are your biggest issues with learning D? I've got the 
feeling that many in the D community expect a C++ background from 
newcomers and we might need some material that lowers the barrier 
for people coming from say python.

And I'd advice you to get a good frontend for gdb :-) It really 
makes a difference.