Re: D / GtkD for SQL Server

2013-10-25 Thread John Joyus
On 10/24/2013 10:28 PM, Adam D. Ruppe wrote: On Tuesday, 22 October 2013 at 06:33:04 UTC, John Joyus wrote: That works! Thanks. cool. If you need anything more in this, let me know (feel free to email me directly too destructiona...@gmail.com ) and i'll see what I can do. That is great!

Re: Trouble with destroy

2013-10-25 Thread Namespace
On Monday, 23 September 2013 at 19:11:53 UTC, Namespace wrote: On Monday, 23 September 2013 at 19:06:48 UTC, Namespace wrote: Code: import std.stdio; struct A { public: int[4] val; alias val this; } void main() { A a; a.destroy(); }

Re: D / GtkD for SQL Server

2013-10-25 Thread Gary Willoughby
On Sunday, 20 October 2013 at 08:13:35 UTC, John Joyus wrote: I am learning D and itching to create some small tools (basically Windows executables) for our internal use, but any tool I think of creating also needs some support for SQL Server! So my question is: 1). Does D has any support

Re: Sql - Any tuto ?

2013-10-25 Thread Gary Willoughby
On Saturday, 10 August 2013 at 18:28:31 UTC, H. S. Teoh wrote: In that case, it should be written like this: ... command.prepare(); scope(exit) command.releaseStatement(); ulong rowsAffected; foreach ... This is exactly the kind of situation scope

Re: Sql - Any tuto ?

2013-10-25 Thread simendsjo
On Friday, 25 October 2013 at 08:07:02 UTC, Gary Willoughby wrote: On Saturday, 10 August 2013 at 18:28:31 UTC, H. S. Teoh wrote: In that case, it should be written like this: ... command.prepare(); scope(exit) command.releaseStatement(); ulong rowsAffected;

how to tell whether we are running inside a try/catch block?

2013-10-25 Thread Timothee Cour
is there a way to tell whether we're running inside a try/catch block, as well as the type T expected by the catch(T) block (and perhaps also file/line info) ? use case: i'd like to customize my exception handler so that if I'm not running in a try/catch block, then I will pause instead of

Re: Trouble with destroy

2013-10-25 Thread Dicebot
On Friday, 25 October 2013 at 07:29:16 UTC, Namespace wrote: Because this solution does not work anymore with dmd 2.064 beta: Are there any other tips and tricks? File regression and write to dmd beta mail list. It is clearly lack of extra constraint on `T : U[n]` overload (it should

Re: Trouble with destroy

2013-10-25 Thread Namespace
On Friday, 25 October 2013 at 11:10:03 UTC, Dicebot wrote: On Friday, 25 October 2013 at 07:29:16 UTC, Namespace wrote: Because this solution does not work anymore with dmd 2.064 beta: Are there any other tips and tricks? File regression and write to dmd beta mail list. It is clearly lack of

Re: Trouble with destroy

2013-10-25 Thread Dicebot
On Friday, 25 October 2013 at 12:09:34 UTC, Namespace wrote: http://forum.dlang.org/thread/bug-1134...@http.d.puremagic.com%2Fissues%2F K, I have sent a mail to beta list pointing to it. IMHO `destroy` constraints need to be much more strict as destroying only part of object via `alias this`

Re: selectively running unittest functions

2013-10-25 Thread Dicebot
I strictly believe any unittest enhancing library must be built on top of existing unittest blocks using __traits(getUnittest) and be 100% compatible with normal `-unittest` mode

Re: selectively running unittest functions

2013-10-25 Thread Daniel Davidson
On Friday, 25 October 2013 at 13:04:03 UTC, Dicebot wrote: I strictly believe any unittest enhancing library must be built on top of existing unittest blocks using __traits(getUnittest) and be 100% compatible with normal `-unittest` mode I don't disagree. What exactly does that mean and what

Re: selectively running unittest functions

2013-10-25 Thread Dicebot
On Friday, 25 October 2013 at 13:23:46 UTC, Daniel Davidson wrote: What I'm missing, and apparently others in the original thread, is a way to run tests selectively. It is difficult to do with unittest because they are not named. If there were a way to annotate the test and pull them out that

Re: selectively running unittest functions

2013-10-25 Thread Dicebot
On Friday, 25 October 2013 at 13:30:54 UTC, Dicebot wrote: You can completely re-implement default test by using runtime hook http://wiki.dlang.org/Runtime_Hooks (_d_unittest should do AFAIK) *default test runner

Re: how to tell whether we are running inside a try/catch block?

2013-10-25 Thread Ali Çehreli
On 10/25/2013 04:12 AM, Timothee Cour wrote: the stack would already be unwinded and there'd be no way to go back in time to the point where the relevant exception got thrown. Another spot is the constructor of the exception. We print the stack contents by libunwind in a C++ project.

Re: selectively running unittest functions

2013-10-25 Thread simendsjo
On Friday, 25 October 2013 at 14:14:39 UTC, Dicebot wrote: This will work starting with 2.064: module a; import std.stdio; struct ID { string data; } @ID(one) unittest { writeln(1); } @ID(two) unittest { writeln(2); } void main() { import std.typetuple; alias tests =

Re: selectively running unittest functions

2013-10-25 Thread Gary Willoughby
On Friday, 25 October 2013 at 13:04:03 UTC, Dicebot wrote: I strictly believe any unittest enhancing library must be built on top of existing unittest blocks using __traits(getUnittest) and be 100% compatible with normal `-unittest` mode I agree, this should be easy to implement. In my unit

Re: selectively running unittest functions

2013-10-25 Thread Dicebot
On Friday, 25 October 2013 at 15:55:11 UTC, Gary Willoughby wrote: For information how to implement your own unit test handler see the bottom of the report module here: https://github.com/nomad-software/dunit From there you can selectively run tests based on some outside criteria. I think

Just noticed something interesting in the std.allocator source...

2013-10-25 Thread Gary Willoughby
Just noticed something interesting in the std.allocator source, right at the very bottom. An EOF and some code? Does the compiler stop at the EOF? If so why add code beyond that? Also version(none), eh? https://github.com/andralex/phobos/blob/allocator/std/allocator.d#L4071 What's going on

Re: selectively running unittest functions

2013-10-25 Thread Gary Willoughby
For information how to implement your own unit test handler see the bottom of the report module here: https://github.com/nomad-software/dunit From there you can selectively run tests based on some outside criteria. I think the new trait will open up further possibilities too.

Re: Just noticed something interesting in the std.allocator source...

2013-10-25 Thread Brad Anderson
On Friday, 25 October 2013 at 16:03:24 UTC, Gary Willoughby wrote: Just noticed something interesting in the std.allocator source, right at the very bottom. An EOF and some code? Does the compiler stop at the EOF? If so why add code beyond that? Also version(none), eh?

Re: selectively running unittest functions

2013-10-25 Thread Daniel Davidson
On Friday, 25 October 2013 at 14:14:39 UTC, Dicebot wrote: This will work starting with 2.064: Ok. I'll keep pressing. Here is an updated version: http://pastebin.com/g6FWsTkr The idea is to be able to just import ut, annotate as you have described and get unit tests run. I want to mixin

ushort arithmetic question

2013-10-25 Thread Jonathan Crapuchettes
Shouldn't this code work? Looking at the arithmetic conversions section of http://dlang.org/type.html, point 4.1 makes me think that I shouldn't be getting the error since they are the same type. void main() { ushort v1 = 1; ushort v2 = 1; ushort v3 = v1 + v2; } test.d(5): Error:

Re: ushort arithmetic question

2013-10-25 Thread Ali Çehreli
On 10/25/2013 11:45 AM, Jonathan Crapuchettes wrote: Shouldn't this code work? Looking at the arithmetic conversions section of http://dlang.org/type.html, point 4.1 makes me think that I shouldn't be getting the error since they are the same type. void main() { ushort v1 = 1; ushort

Re: ushort arithmetic question

2013-10-25 Thread Jonathan Crapuchettes
On Fri, 25 Oct 2013 11:51:03 -0700, Ali Çehreli wrote: On 10/25/2013 11:45 AM, Jonathan Crapuchettes wrote: Shouldn't this code work? Looking at the arithmetic conversions section of http://dlang.org/type.html, point 4.1 makes me think that I shouldn't be getting the error since they are the

Re: selectively running unittest functions

2013-10-25 Thread Daniel Davidson
On Friday, 25 October 2013 at 16:43:23 UTC, Daniel Davidson wrote: On Friday, 25 October 2013 at 14:14:39 UTC, Dicebot wrote: This will work starting with 2.064: Ok. I'll keep pressing. Here is an updated version: http://pastebin.com/g6FWsTkr The idea is to be able to just import ut,