Refactor set_token.

[1uc]

Currently, one must call set_token in nmodl.yy to have information about where the token appears in the MOD file. Since, it's manual, it's rarely used, and many nodes of the initial AST don't have any token information associated with them.

For example FUNCTION and PROCEDURE blocks have their ModToken set, while NET_RECEIVE doesn't.

nmodl/src/parser/nmodl.yy

Lines 1496 to 1506 in 5abff4f

	procedure_block : PROCEDURE NAME_PTR "(" optional_argument_list ")" units statement_list "}"
	{
	$$ = new ast::ProcedureBlock($2, $4, $6, $7); $$->set_token($1);
	}
	;
	net_receive_block : NETRECEIVE "(" optional_argument_list ")" statement_list "}"
	{
	$$ = new ast::NetReceiveBlock($3, $5);
	}

Instead of fixing all occurences using the current API, we could consider changing the ctors for AST nodes such that they expect the ModToken (describing the location) as their first argument, and then the additional arguments. This way the compiler will complain about any omissions.