2008/1/10, Ted Kremenek <[EMAIL PROTECTED]>: > Besides just checking in the file, I was wondering if it would be > possible for you to do a few other things as well: > > 1) Could you add an explicit check in 'ccc' for no command line > arguments? > > ([EMAIL PROTECTED]:Downloads)$ gcc > i686-apple-darwin9-gcc-4.0.1: no input files
Done. > 2) To house the script we should probably create a new subdirectory in > the clang tree; e.g. "utils". Done. > 3) Please add the LLVM copyright notice to the top of the file: Done. > 4) A brief comment at the top of the file (below the copyright notice) > about what the script does. I'm still uncomfortable with writing English, but: "This script attempts to be a drop-in replacement for gcc." > 5) Add a (brief) blurb to the web page about the script. This can be > done by editing the appropriate files in "www". The blurb can be very > minimal, but this is a good way for people to know that the script > exists. You can also mention a few limitations/requirements for the > script to work. > > I am more than happy to do (5) myself. I'm not an expert on Python, > so I would prefer that you modified the script file yourself (1-4). Okay, I'm not sure where to add the blurb, so I defer to your better judgement. :) -- Seo Sanghyeon _______________________________________________ cfe-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
