@scknkkrer that ticket is probably not an easy one if you haven't done a lot of work on the compiler before

Actually, I’ve handle it well.

the two patches you have there are not the right way to approach the problem

But, if there are exceptions like . and ..; I have to know.

Oh.

you should not be doing anything in parse-invoke for that ticket

I’m listening.

I'm going to reiterate one more time - this is an advanced ticket

before doing any more work, you should write a comment to describe exactly what you're intending to do to address the problem

it maybe also be that the scope is too wide and invasive for one ticket

but at the moment it's impossible to tell because there's no description of the problem besides my original annoyance

that deftype methods that start a . don't error and produce bad runtime code

@scknkkrer that ticket was badly described

which was my own fault - I've left a better description

So, you are saying that just deftype methods has to be limited against that check ?

I've also clarified where I think this might be meaningful

let's step back a second

(.foo ...) is nearly always fine

it's just a method call - there's no checking to do of any kind

(deftype Foo Object (.bar [] ...))

No, it was my fault. I should asked about it.

can't possible work

and the question is simply whether there are other similar cases

and whether the work could be combined - but maybe it can't

and we need separate tickets

**I’ve had should asked about it.

Ok, boss. I’m still volunteer for this problem.