I'm tracking down a problem with the new build-torque.xml I'm putting together and when scanning the templates, man, they're ugly. Here are some example variable names:
cjtype, cfc, clo, v, relCol, colFK, relCol2 Out of context (which means, anybody who didn't write the code or hasn't studied it for a good length of time) these names mean nothing (okay, you could probably guess colFK = columnForeignKey and relCol = relationColumn). And I did pick some of the worst. But regardless, going forward with patches and what not, can we start using Java-style names? E.g. columnJavaType and columnJavaName (so that's what cfc is...) or even colJavaType/colJavaName, though I personally prefer the first two. I had thought the Java community had an understanding to leave the C/C++ style of picking awful variable names behind. I wouldn't think we'd have to abandon this merely because the templates are Velocity. This is a viable suggestion? Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
