Re: [PATCH, fortran] Constraints for equivalence members and privatetypes - Ping

[Paul Thomas <paulthomas2 at wanadoo dot fr>]

I know that preventing gfortran from doing things might not be the 
flavour of the month but might I remind you all of this patch and a 
question it contained?

> As a general remark, I had started to implement the constraints in symbol.c(check_conflict) but found that the majority of the equivalence constraints were to be found in resolve.c. I therefore elected to put the rest there too.
In fact it was not just the majority but all those that could not be put 
in match.c.  ASFAIK the reason is that half of the constraints, which 
involve more than one symbol, sit most naturally in resolve.c and the 
single symbol constraints have been put with them for convenience.  I 
have a version ready to go that puts these latter in check_conflict.

Note that both versions exist and so it would be no extra work to submit 
either.  What do you want?

> I have only made the constraint on equivalence mixing of numeric/character/structure subject to the -std=f95 option for g77 compatibility. I do not think that this would make any sense for any of the others but I am open to suggestions there.
I have moved on with this point, having re-read the F95 standard.  I 
have now implemented a check of sequences to see of what type they are 
and allow numeric[/character] sequences to be mixed with 
numeric[/character] variables, when -std=f95 is used.  I have not 
checked that the types are default.

This patch will, therefore, be resubmitted tonight or tomorrow.

Best regards

Paul T