Anyway, I've updated autoCall(), so now you can pass arguments like usual but also specify the names of any ref/out variables that will be created. It will also check to make sure the number of arguments matches for the call to the function. Of course, arguments have to be evaluable at compile time (You can't just pass a string, it has to be immutable). Here's the code:<br>
<br>import std.file; // getTimes()<br>import std.conv; // to!string()<br>import std.traits; // Parameter types, storage, introspection<br><br>import std.stdio;<br><br>// Notes:<br>// Currently it only works with simple built-in types:<br>
// Integrals, strings, but not objects.<br>//<br>// It will throw a compiler error and a message if there are unmatched<br>// number of arguments for the call to func().<br>// Arguments have to be evaluable at compile time.<br>
auto autoCall(alias func, T...)(T args)<br>{<br> alias ParameterStorageClass STC; // storage class enum<br> alias ParameterTypeTuple!(func) paramTypes; // types of parameters<br> alias ParameterStorageClassTuple!(func) storageTypes; // storage class of parameters<br>
<br><br> static if (paramTypes.length != args.length)<br> {<br> pragma(msg, "autoCall: Template Error: Unmatched number of arguments for call to " ~ __traits(identifier, func) ~ "()");<br>
static assert(0);<br> }<br> <br> string declString, callString;<br> <br> // eg: callString = "funcName("<br> callString = __traits(identifier, func) ~ "(";<br> <br> foreach (int i, storageType; storageTypes)<br>
{<br> if (storageType == STC.OUT || storageType == STC.REF)<br> {<br> // eg: declString ~= "int newParamName; "<br> declString ~= paramTypes[i].stringof ~ " " ~ args[i] ~ "; ";<br>
<br> // eg: callString = "funcName(" ~ "newParamName,"<br> callString ~= " " ~ args[i] ~ ",";<br> }<br> else<br> {<br> // Fetch the value of args or args[i] and expand it to callString.<br>
// We cannot use the actual names of the arguments since that would<br> // not work with literals (unless we added tests and more branching)<br> <br> // need to use static if here due to array bounds checking<br>
static if (args.length == 1)<br> {<br> // eg: callString = "funcName(args, newParamName,"<br> callString ~= '"' ~ to!string(args) ~ '"' ~ ",";<br>
}<br> else<br> {<br> // eg: callString = "funcName(args[i], newParamName,"<br> callString ~= '"' ~ to!string(args[i]) ~ '"' ~ ",";<br>
}<br> }<br> }<br> <br> // remove the extra comma and close the call string<br> callString = callString[0 .. $ - 1] ~ ");";<br><br> // return joined strings ready to be used with mixin()<br>
return declString ~= callString;<br>}<br><br>void testMe(string x, ref int z, string y)<br>{<br> writeln(x, y);<br> z = 5;<br>}<br><br>unittest<br>{ <br> immutable string var1 = "foo";<br> immutable string var2 = "bar";<br>
<br> mixin(autoCall!(testMe)(var1, "newvar", var2));<br> assert(newvar == 5);<br>}<br><br>void main() { }<br><br>Fun stuff, right? :p<br><br><div class="gmail_quote">On Sat, Aug 7, 2010 at 9:57 PM, Andrej Mitrovic <span dir="ltr"><<a href="mailto:andrej.mitrovich@gmail.com">andrej.mitrovich@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Cool stuff! I'll have a look later. Thanks.<div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Sat, Aug 7, 2010 at 9:53 PM, Nick Sabalausky <span dir="ltr"><a@a.a></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
"Andrej Mitrovic" <<a href="mailto:andrej.mitrovich@gmail.com" target="_blank">andrej.mitrovich@gmail.com</a>> wrote in message<br>
news:mailman.175.1281208901.13841.digitalmars-d@puremagic.com...<br>
<div>> You know, I just had an idea. It would be really cool to have some sort of<br>
> generalized template function which can test other functions in various<br>
> ways. You could pass strings as options, where you might choose the type<br>
> of<br>
> testing being done, such as verification tests or performance tests.. Or<br>
> if<br>
> a function is designed to write a file on disk, maybe you'd want to have<br>
> an<br>
> option for the maximum number of tests to run on that function (you don't<br>
> want to be left with 10000 files written in some temp directory<br>
> somewhere..), or a test to see if a function will fail with invalid input,<br>
> etc.<br>
><br>
> Well it's just an idea, I better take a look at the existing test<br>
> frameworks<br>
> and see how it's done there.<br>
><br>
<br>
</div>Probably not quite as fancy as what you're talking about, but my SemiTwist D<br>
Tools library has a module that includes something that's similar to assert<br>
but:<br>
<br>
- Allows to you verify that a particular statement throws a particular type<br>
of exception.<br>
- Properly reports if an expression throws (and you didn't expect it to).<br>
- Doesn't abort the program on failure.<br>
- Reports "expected" expression and "actual" value.<br>
<br>
<a href="http://www.dsource.org/projects/semitwist/browser/trunk/src/semitwist/apps/tests/deferAssertTest/main.d" target="_blank">http://www.dsource.org/projects/semitwist/browser/trunk/src/semitwist/apps/tests/deferAssertTest/main.d</a><br>
<a href="http://www.dsource.org/projects/semitwist/browser/trunk/src/semitwist/util/deferAssert.d" target="_blank">http://www.dsource.org/projects/semitwist/browser/trunk/src/semitwist/util/deferAssert.d</a><br>
<br>
It does need some clean-up and improvements, but it at least works.<br>
(Although, trunk is currently in the process of switching from D1/Tango to<br>
D2/Phobos, so the latest revisions might be broken and it definitely doesn't<br>
take advantage of D2-specific features yet. But the version included with<br>
Goldie 0.3 does work fine on D1/Tango though).<br>
<br>
<br>
</blockquote></div><br>
</div></div></blockquote></div><br>