From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Denk Date: Wed, 24 Aug 2011 14:49:51 +0200 Subject: [U-Boot] [RFC] New init sequence processing without init_sequence array In-Reply-To: References: <1313587343-3693-1-git-send-email-graeme.russ@gmail.com> <20110822201023.0F8A111EF9D9@gemini.denx.de> <20110823114920.AD2ED201520@gemini.denx.de> <20110824053849.2317F11F9E75@gemini.denx.de> <20110824064819.0529D11F9E76@gemini.denx.de> Message-ID: <20110824124951.3FA2C11F9E75@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Graeme Russ, In message you wrote: > > > Agreed. I should have written: I have a _readable_ source file that > > can be parsed without additional tools. > > I would hardly call 'grep' an extra tool - How many programmers do you > know that have never used grep? That's not the point. There is a significant difference between seeng the source code in your favorite editor or in the source code window of your debugger's GUI or even some IDE, versus having to run additional commands in a separate window. > And by defining #DEBUG I can have a parallel list of function names so when > the loop picks up the next funtion pointer, it picks up the name as well > ready to examine before stepping in - OK, not ideal, but still, I think > the flexibility to seamlessly inject init functions at the board level > outweighs this Sorry, but when reading the source code or when revioewing patches I cannot paick up any next funtion pointers, I'm stuck with reading the source code only. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence. -- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5