search

npalix / rathaxes

Automatically exported from code.google.com/p/rathaxes
1 stars 0 forks source link

Do some magic to avoid identifiers conflicts #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, the management of the identifiers in each backend template is void, 
and will soon be done through rathaxes functions generating unique identifiers.

In a far future, It would be nice to have a pass on the backend's tree, to 
modify the identifiers used each time there is a confliting name with a parent 
tree, in order to allow using the same identifiers in differents templates 
without risking any conflict at frontend compilation.

To sum it up :
Some magic is required to make every single identifier unique, but that should 
be for much later, as we need first some functional features :)

Original issue reported on code.google.com by dav.pineau@gmail.com on 9 Jul 2011 at 12:46

GoogleCodeExporter commented 9 years ago

Original comment by dav.pineau@gmail.com on 13 Apr 2012 at 11:47