Hi Bernard, > My program scans all Idl files to create a Delphi unit containing all > constants (adapting constant names and declarations to Delphi syntax). > My program did not expect these constructs in the Idl file: > > const long TABLE = com::sun::star::sdb::CommandType::TABLE; > const long QUERY = com::sun::star::sdb::CommandType::QUERY; > > Of course it is possible (but more complex) to recognize a constant from > another Idl, but what would you do if it refers to an Idl file that you > have not yet scanned ? Forward reference may become a real problem if > this kind of dependency is widely used.
There should be an include directive in the file, pointing to CommandType.idl. So your tool probably should scan included files, too. This shouldn't be a problem, since cyclic references should not happen (else the regular IDL compiler would already complain). Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
