vibe.d 0.7.9 released

[Rob T]

On Wednesday, 31 October 2012 at 16:19:01 UTC, Sönke Ludwig 
wrote:
> Am 31.10.2012 17:11, schrieb Rob T:
>> On Wednesday, 31 October 2012 at 06:59:45 UTC, Sönke Ludwig 
>> wrote:
>>> Changes:
>>>
>>>  - New HTML form interface generator similar to the REST 
>>> interface
>>>    generator that simplifies web front end development:
>>>    http://vibed.org/api/vibe.http.form/registerFormInterface
>>>    (thanks to Robert Klotzner aka eskimor)
>>>
>>>  - Diet HTML templates now support includes and recursive
>>>    blocks/extensions
>>>
>>>  - The REST interface generator has got a new method to 
>>> reference types
>>>    in the generated string mixin, which makes it more robust 
>>> to user
>>>    defined types (thanks to Mihail Strašun aka mist)
>>>
>>>  - Now includes API docs for offline viewing
>>>
>>>  - A lot of small fixes and improvements
>>>
>>>
>>> Full change log: 
>>> http://vibed.org/blog/posts/vibe-release-0.7.9
>>>
>>> Download: http://vibed.org/download?file=vibed-0.7.9.zip
>> 
>> To build Vibe.d you are using DMD 2.060 as released here? I'm 
>> just
>> wondering what you found to be the best DMD version, or if you 
>> are using
>> a newer pre-released version found in git? Thanks.
>> 
>> --rt
>> 
>
> I'm using the standard 2.060 release. But I know that several 
> people
> also use it with the git master version.

I'm relatively new to D but making good progress with it after a 
very slow start (it is a very complex language). Some of what I 
am working on shares similarities with what vibe.d is doing, so 
I'm very interested in how vibe.d is progressing.

vibe.d looks like a rather complex project, so I am wondering if 
you've made use of any shared libs with D (i.e., .so and/or .a 
compiled for PIC)?

I know that the druntime will not link as-is without a rebuild to 
enable PIC, so have you found this to be a problem, not using 
shared libs, or have you rebuilt druntime to allow for it?

I'm also wondering how the co-routines are working out with vibe? 
I thought of using them, but my current design will be using 
message passing instead, where the code is broken up into small 
parts to perform the co-processing. When messages are received at 
a location, the code fragment executes. I've done this before in 
C++ and it worked great, but with D I now have an alternative 
using fibers, but I have no exerience with using them.

Thanks for any input you can provide.

--rt