Guido van Rossum wrote: > > > This is pure cosmetics, but I found that the latest CVS versions > > of the Parser Makefile have become somewhat verbose. > > > > Is this really needed ? > > Like what? What has been added? I was referring to this output: making Makefile in subdirectory Modules Compiling (meta-) parse tree into NFA grammar Making DFA for 'single_input' ... Making DFA for 'file_input' ... Making DFA for 'eval_input' ... Making DFA for 'funcdef' ... Making DFA for 'parameters' ... Making DFA for 'varargslist' ... Making DFA for 'fpdef' ... Making DFA for 'fplist' ... Making DFA for 'stmt' ... Making DFA for 'simple_stmt' ... Making DFA for 'small_stmt' ... ... Making DFA for 'list_for' ... Making DFA for 'list_if' ... Adding FIRST sets ... Writing graminit.c ... Writing graminit.h ... > > Also, I'd suggest adding a line > > > > .SILENT: > > > > to the top-level Makefile to make possible errors more visible > > (without the parser messages the Makefile messages for a clean > > run fit on a 25-line display). > > I tried this, and it's to quiet -- you don't know what's going on at > all any more. If you like this, just say "make -s". I know, that's what I have in my .aliases file... just thought that it might be better to only see problems rather than hundreds of OS commands. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4