| 
     
      
      
      From: Sven E. <sve...@we...> - 2001-10-02 06:57:54
      
     
   | 
Say we would have in addition to the --hact --ise --se --ve commandline options a --xml commandline option. When specified it would produce an xml file instead of an ace/esd file for the specific compilers. On this xml file an xsl transformation could be run applying specific xsl files like hact.xsl, ise.xsl, se.xsl, ve.xsl, special_se.xsl, ... . The output would be ace/esd files for the specific compilers (of course it could produce other things as well). This would allow application developers to customize the form of the produced output file. For elj applications for example I currently cut and paste certain areas into the produced se.ace file. What has to done by hand could then be done within the xsl. Using the facility it would even be possible for a elj_se.xsl to "inherit" from the se.xsl and just redefining the special things. geant's task could be used to apply the xsl transformation in a convenient and automated way. What do you think? - Sven ________________________________________________________________ Flug.de - Beste Verbindungen in alle Welt http://flug.de/sb/?PP=0-5-100-105-15  |