Supplement：

function Validator(CtrlID) {

var obj = $("#" + CtrlID);
var settings = obj.data("settings");
var _IsValid = true,_CtrlValue = "";
_CtrlValue = obj.val();
if (!_IsValid){
    if (typeof (eval(settings.CustomFunction)) == "function") {
        eval(settings.CustomFunction + "(settings,_CtrlValue)");
    }
}   

}

AjaxMin：

function Validator(n){var i=$("#"+n),t=i.data("settings"),u=!0,r="";r=i.val(),u||typeof eval(t.CustomFunction)=="function"&&eval(t.CustomFunction+"(settings,_CtrlValue)")}


Should be correct：

function Validator(n){var i=$("#"+n),t=i.data("settings"),u=!0,r="";r=i.val(),u||typeof eval(t.CustomFunction)=="function"&&eval(t.CustomFunction+"(t,r)")}

By default AjaxMin assumes eval statements are safe and do not reference local variables -- for instance, for generating JSON objects, etc. The sample code is obviously not in that class. For this code to compile correctly, you need to specify one of the other -evals switches: for this particular instance, since the settings and _CtrlValue variables are in the same scope as the eval statement, try -evals:immediate. If those variables were outside the scope of the eval statement, you would have to use -evals:safeall.

Please see the documentation tab, "Problems with evals" article for more information on how to fix this. Just a simple command-line switch that needs to be set.