Hi Cedric,
Great start! To facilitate development and evaluation of this system,
could you please do the following:
* import a new CVS module called hackySCLC
* create a src/ directory containing your version of sclc.pl
* create a lib/examples directory containing files of example code in a
variety of languages. Relatively short files of Java, C, C++, Matlab, and
Fortran would do for starters. Mike, can you help supply Cedric with some
sample code ASAP?
* create a build.xml file. For starters, the default target should simply
invoke the sclc.pl program on the example code, putting the resulting XML
in the build/ directory. Later, we can augment this into a testing
framework (save "correct" versions of the XML files, run the sclc version,
and compare the output to the oracle versions, etc.)
* create a README.html file that gives pointers to installation of PERL and
any required libraries.
Once this is done, it will be easy for all of us to see the XML that is
generated by different languages, contribute new example code to see what
happens, and simplify testing and evolution. Please let us know when this
is available so we can check it out!
Cheers,
Philip
--On Thursday, August 18, 2005 1:43 AM -1000 "Qin ZHANG (Cedric)"
<[EMAIL PROTECTED]> wrote:
Hi,
I hacked the original script and now it outputs xml instead of plain
text. Usage is still the same. Please notice that this is just a
proof-of-concept hack, not the final product.
Please try it and let me know what needs to be improved. At this stage, I
am more interested in user requirements, such as what should command line
option be and what should the xml output be.
The script uses perl XML::DOM library. If you are on a recent linux
distribution, you should be ok. If you are on windows using active state
perl, you need to download the libary from www.cpan.org yourself.
Thanks.
Cedric
