search for: nindent

I have run Nindent, the reformatting script, over all the C code, *except* HDT and externally maintained code (gPXE, libpng, tinyjpeg, zlib, and LZO). I'll leave it up to Erwan and Pierre to do gPXE. Please help clean up any stupidities when you see them. Especially asm() statements are quite butchered by Nind...

I have pulled in Stefan Bucur's updated elflink branch into the main Syslinux repository as the "elflink" branch, and fixed a couple of minor issues. Note in particular that I have *not* run Nindent over the sources... I will leave that to Stefan and Klaus unless there is a compelling reason to. Please note the following, however: int foo(); ... in C doesn't mean a function with no parameters. That is written: int foo(void); In C, "int foo();" means the same as "int fo...

...of the code for this patch. Thank you. You can get those patches from Shao's git repo (chain_isolinux branch): [chain] Add support for chain-loading another isolinux.bin http://git.etherboot.org/?p=people/sha0/syslinux.git;a=commit;h=39adcc6d820d6432034c901f64a43dcd011ef1c3 [chain] Run Nindent on chain.c chain_isolinux http://git.etherboot.org/?p=people/sha0/syslinux.git;a=commit;h=4b4cfe0cd38d6ab371f58d76a171b5edcffd9787 - Gert Hulselmans

...eeLdr Use something like: LABEL freeldr COM32 chain.c32 APPEND freeldr=freeldr.sys Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca> --- Author: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sun May 1 12:43:09 2011 -0400 chain: Run Nindent on chain.c Minor formatting fix-ups Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>

So far, the consensus seem to be: - Devel list is not desirable at this time. I will continue to post major announcements to syslinux-announce, of course. - The 4-space coding standard seems to get most favor. I would like to run reformatting jobs immediately after the 3.81 release; the expectation is that other people will run the same reformatting on any code merged after that point

> Looking around, there appear to be a lot of small places needing some > whitespace cleanup/reconciliation. > Just to be clear, I am not criticizing, but actually asking... Are those white-space characters impacting the binaries being built? Would they affect common users? Are those characters affecting developers? For instance, do they affect some git command? Or, do they make