vexorian
commented
11 years ago With that patch, my template now looks like this:
#include <bits/stdc++.h>
using namespace std;
struct ${ClassName}
{
${if Method.ReturnType.LongInteger}${if Method.ReturnType.Array}vector${else}long${end}${else}${Method.ReturnType}${end}${--
} ${Method.Name}(${foreach Method.Params p , }${if p.Type.LongInteger}${if p.Type.Array}vector${else}long${end}${else}${p.Type}${end} ${p.Name}${end})
{
return ${Method.ReturnType;ZeroValue};
}
};
${CutBegin}
${<TestCode}
${CutEnd}
It is a bit messsy, but it works, and now vector
A configuration entry to replace the "long long" text with something else would have made a cleaner template (and other people might find it useful, I heard some like to change it with int64), but perhaps would be overkill for such a singular issue.
zen0wu
wookayin
A nitpick of mine is to use long and not long long (not very clean). The TC server now accepts long, so it is perfectly possible. But Greed sends the type as long long and there is no way in configuration to change this.
So i was trying to do it with template conditionals. Although the jmte page says that you can use = operator to compare string literals, it is not really working for me:
${if Method.ReturnType = "long long" } long ${end}This would be perfect if it worked, but it seems that the condition returns true regardless of the string literal. I am not able to find good examples for how to do comparisons in jmte.
An elegant way to fix this in the plugin (if it is really impossible to do it with templates) would be to add a .LongInteger to the type predefined variables like .RealNumber and .String
Edit: After much attempts to do it with templates, I ended up concluding that changing code is an easier solution. This pull request adds a variable that can be used in Templates to determine if an argument is 64 bits integer. Also adds a configuration point to replace "long long" with another thing. Some guys prefer to use LL, or int64 (with a typedef), so maybe it is useful for all.