Edgecase with global structs, tasks with same name as that struct

[shanereetz]

Explanation

There's an edge-case where a global struct could collide with a task, if the task had the same name as the global struct.

Example:
Program with local var: Task:var (note the colon)
Global with the same name: Task.var

While this isn't common, as a global ideally has the g prefix (i.e. gVar), it is a case that the current code does not support. The values would be overwritten ask "Task:var" and "Task.var" are treated identically in parsing.

Potential Solution

Somehow maintain the data that "Task:" is a task, not a global.