digitalmars.D.announce - Release vibe.d 0.7.30
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (19/19) Oct 31 2016 Main changes over 0.7.29:
- Saurabh Das (2/20) Nov 01 2016 I'm going to try this out today! :)
- Saurabh Das (3/6) Nov 01 2016 How can I find out more information about the 'runApplication'
- Jacob Carlborg (8/10) Nov 01 2016 I think it should say something like: "slowly fading out the default
- Jacob Carlborg (5/13) Nov 01 2016 For reference, here's the commit that introduced the change:
- John Colvin (3/13) Nov 01 2016 Is "phasing" the word that's being looked for here? I.e. "slowly
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (2/15) Nov 01 2016 Yes that sounds better. I'll change it and complete that partial sentenc...
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (6/13) Nov 01 2016 A summary would be:
Main changes over 0.7.29:
- Compiles on the latest DMD version (2.068.x-2.072.0)
- Added a new authorization framework for the web/REST interface
generators
- Extended the serialization framework with more hooks and traits,
enabling the use of custom UDAs - vibe-sdlang [1] is an SDLang
serialization module that became possible this way
- opDispatch has been removed from Bson/Json
- Optional support for using diet-ng [2] has been added and is
enabled by default for new projects - for existing projects, add
diet-ng as a dependency or add it to dub.selections.json
- The HTTP client can now be used on Unix socket destinations
- Added table support for the Markdown compiler
All changes:
https://vibed.org/blog/posts/vibe-release-0.7.30
DUB package:
https://code.dlang.org/packages/vibe-d/0.7.30
[1]: https://code.dlang.org/packages/vibe-sdlang
[2]: https://code.dlang.org/packages/diet-ng
Oct 31 2016
On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:
Main changes over 0.7.29:
- Compiles on the latest DMD version (2.068.x-2.072.0)
- Added a new authorization framework for the web/REST
interface
generators
- Extended the serialization framework with more hooks and
traits,
enabling the use of custom UDAs - vibe-sdlang [1] is an
SDLang
serialization module that became possible this way
- opDispatch has been removed from Bson/Json
- Optional support for using diet-ng [2] has been added and is
enabled by default for new projects - for existing
projects, add
diet-ng as a dependency or add it to dub.selections.json
- The HTTP client can now be used on Unix socket destinations
- Added table support for the Markdown compiler
[...]
I'm going to try this out today! :)
Nov 01 2016
On Tuesday, 1 November 2016 at 09:09:05 UTC, Saurabh Das wrote:On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?[...]I'm going to try this out today! :)
Nov 01 2016
On 2016-11-01 12:20, Saurabh Das wrote:How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d. -- /Jacob Carlborg
Nov 01 2016
Jacob Carlborg <doob me.com> On 2016-11-01 13:47, Jacob Carlborg wrote:On 2016-11-01 12:20, Saurabh Das wrote:For reference, here's the commit that introduced the change: https://github.com/rejectedsoftware/vibe.d/commit/f7ba59a6c80dc85882654138087bad579480cadf -- /Jacob CarlborgHow can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d.
Nov 01 2016
On Tuesday, 1 November 2016 at 12:47:13 UTC, Jacob Carlborg wrote:On 2016-11-01 12:20, Saurabh Das wrote:Is "phasing" the word that's being looked for here? I.e. "slowly phasing out the default main".How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d.
Nov 01 2016
Am 01.11.2016 um 14:29 schrieb John Colvin:On Tuesday, 1 November 2016 at 12:47:13 UTC, Jacob Carlborg wrote:Yes that sounds better. I'll change it and complete that partial sentence.On 2016-11-01 12:20, Saurabh Das wrote:Is "phasing" the word that's being looked for here? I.e. "slowly phasing out the default main".How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d.
Nov 01 2016
Am 01.11.2016 um 12:20 schrieb Saurabh Das:On Tuesday, 1 November 2016 at 09:09:05 UTC, Saurabh Das wrote:A summary would be: runApplication does the same as runEventLoop, plus performing command line finalization and privilege lowering. This is the same that VibeDefaultMain otherwise does, with the only difference that it is invoked with an explicit function call.On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?[...]I'm going to try this out today! :)
Nov 01 2016