I have been thinking about how I’m going to do this, and I think I found a solution. I’m going to parse through the whole page with a replace regex, like is frequently done in the process, and replace all strings with <STRING n> where n is a unique, incrementing number, like how when an object is created, its replaced with <CLASS name> temporarily. Then hold all the strings in an array. I will do this before all the parsing begins, and once everything is complete, I will replace all <STRING n>’s with the appropriate string from the array. In this way, I’m masking the strings from the parser. I know the parser can move things around, so I think keeping track of them by a number, than relying on the order in which the strings appear, is a safer way to do it.
The member keyword still works, and I think is finished, I just now have a bug where if in the Processing code someone assigns a private member inside a method, using something like this
this.num = num;