Data Sanitation

Quick opinion question for you:

When you're instantiating an object based on unsafe input from a form in a loosely-typed language, do you leave the sanitation up to the form handler, or to the object?

Ex:

p = new Pokemon();
p.name = sanitize(form.name);
vs.
p = new Pokemon();
p.setName(form.name); // sanitizing code in the method

Adding to this: the object may also be instantiated from safe input in other points of the program. It will directly access the properties when doing this:

p.name = safeInput.name; return p;

To help you find an answer:

what happens if, when sanitizing in the method, you stumble upon invalid input? You can signal the error to the enclosing code with the appropriate mechanism: let's just throw some exception in this case. Should this be handled by the enclosing code? How? Can you let the exception bubble up higher up?

Personally I'd rather handle the error at the site of input because it's usually too late at the site of construction. But remember that's due to the design of GUIs/frameworks/whatever.

You don't mutate state.

>>4
The OP's concern is also valid if/when considering initialization.

>>5
The constructor should just glue up the data structure with its inputs, so (make-structure (sanitize data)).

This way you can reuse sanitize elsewhere.

SANITIZE MY ANUS

>>7
You know, it doesn't sound as good when the words work together like that ...

>>8
fuck you faggot

"sanitize" is another one of those enterprise buzzwords that managers like to throw around.

>>10
I take it you don't shower

>>6
I agree with this.
Also, if you want to pass safe data to the object at a later point (cloning a valid object for example) there is no reason for the sanitasion logic to be in the mutator method.

>>1
I use association lists, instead of classes
map sanitize Object
is enough

>>1
IMHO first example breaks encapsulation, because external functions need to know, what data may be valid or not for Pokemon class. Should this information be part of delivered interface?

>>14
It's what I call "mental masturbation", when you engage is some pointless intellectual exercise that has no possible meaning. -- Linus Torvalds

>>15
First example may leads to problems and need of refactoring in future.
If you don't see it, it's your problem.

Your life may leads to death and need of burying in future.
If you don't see it, it's your problem.

former