> > I've gotten in trouble using spaces in Makefiles where tabs were > > absolutely required. The files look like they should work, but they do > > not. > > Make is evil that way too. > > Actually, the real evil is whoever didn't set a fixed meaning to 0x09 > when making up the standard in the first place.
I'm not sure what this whole thread is about. To me it seems that visual representation (as in "a tab is expanded into n spaces" or "...spaces up to the next predefined tabstop") is mixed with lexicografical meaning (as in "a leading tab denotes a stmt that creates the dependent file" or "a tab is a seperator" - both cases in make). The real problem stems from editors that have no proper visual differentiation between the various types of whitespace (...and users that aren't aware of this fact ;) emacs really is top notch in this arena ;) [for those not familiar with emacs: you can configure it such that different whitespace are displayed in different color] Best wishes Michael -- Michael Gerdau email: [email protected] GPG-keys available on request or at public keyserver
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
