As Barry said, priority is determined by grammar (and there are several operators that do not fit the basic idea of โโpriority very well, so you can only really figure out what happens completely correctly from the grammar, not the priority table).
Even if we ignore it, however, the priority of deletion only (at least usually) determines whether the statement is legal / permitted, and not what it means. To give a counterexample, with + and * , priority determines that 2 * 3 + 4 gives 10, not 14 (i.e. Multiplication takes precedence).
In the case of delete , no value is created as a result of the delete operator; therefore, a statement of the type delete x + y; just not allowed. It will be parsed as (delete x) + y; , but since delete x does not create a value that can be added to anything else, the result is always inhibited (and if you change the statement, this will remain true).
Associativity doesn't really make sense for delete . In particular, associativity deals with what will look like: a @ b @ c like (a @ b) @ c or a @ (b @ c) (where @ is some operator). This is really real for operators that accept two operands. It is simply impossible to combine delete in such a way that you can ask a question (questions) to which associativity answers.
source share