Path parsing in v3 currently switches from state NAME to state TYPE based rather stupidly on the presence of a . in the middle of an accessor/path segment. So parsing //java.home/java.lang.String would try to load java.home as a class. I think I have \ as an escape for that . and maybe in that sense this is already handled but the syntax is kind of gross if so.
Path parsing in v3 currently switches from state
NAMEto stateTYPEbased rather stupidly on the presence of a.in the middle of an accessor/path segment. So parsing//java.home/java.lang.Stringwould try to loadjava.homeas a class. I think I have\as an escape for that.and maybe in that sense this is already handled but the syntax is kind of gross if so.