The tabs vs spaces debate among developers revolves around the preferred method for indentation in code. ‘Tabs’ advocates argue that tabs are semantically correct for indentation, customizable, and more accessible, especially for those with visual impairments. They suggest using tabs for indentation and spaces for alignment. ‘Spaces’ advocates emphasize consistency, as spaces ensure that code formatting appears the same across different editors and platforms, avoiding issues with variable tab sizes. This approach is often preferred in team environments to maintain uniform code appearance.
But if you are programming in the C language and need to use Makefiles, there is no choice — you must use ‘Tabs’.
The requirement for tabs in Makefiles originates from Stuart Feldman, Unix developer and the creator of the ‘make’ utility. Feldman chose tabs to help in distinguishing between commands and other text in the Makefile. Specifically, the Lex parser used in the early implementation of ‘make’ had difficulties distinguishing between tabs and spaces, leading to the mandate for tabs. Although Feldman has acknowledged this as a suboptimal decision, the convention has persisted.
The above screenshot, shows a Makefile. This example is using the ‘show symbol’ feature in notepad — with it you are able to clearly distinguish between tabs and spaces — the arrows indicate that tabs are used on lines 8, 12 and 16. If you indent those lines using spaces instead of tabs, the program will not run — you’ll receive an error:
Makefile:line_number: *** missing separator. Stop.
So, whether you prefer tabs or spaces when you program is up to you. But if you’re working with Makefiles in C, Stuart has left you no choice.
If you haven’t seen the Silicon Valley episode above (S3 Ep6) — give it a watch, as with the entire series, it’s a lot of fun.
Ben Santora — October
The above is the detailed content of Tabs vs Spaces — Makefiles in C. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Yes, function overloading is a polymorphic form in C, specifically compile-time polymorphism. 1. Function overload allows multiple functions with the same name but different parameter lists. 2. The compiler decides which function to call at compile time based on the provided parameters. 3. Unlike runtime polymorphism, function overloading has no extra overhead at runtime, and is simple to implement but less flexible.

C has two main polymorphic types: compile-time polymorphism and run-time polymorphism. 1. Compilation-time polymorphism is implemented through function overloading and templates, providing high efficiency but may lead to code bloating. 2. Runtime polymorphism is implemented through virtual functions and inheritance, providing flexibility but performance overhead.

Yes, polymorphisms in C are very useful. 1) It provides flexibility to allow easy addition of new types; 2) promotes code reuse and reduces duplication; 3) simplifies maintenance, making the code easier to expand and adapt to changes. Despite performance and memory management challenges, its advantages are particularly significant in complex systems.

C destructorscanleadtoseveralcommonerrors.Toavoidthem:1)Preventdoubledeletionbysettingpointerstonullptrorusingsmartpointers.2)Handleexceptionsindestructorsbycatchingandloggingthem.3)Usevirtualdestructorsinbaseclassesforproperpolymorphicdestruction.4

People who study Python transfer to C The most direct confusion is: Why can't you write like Python? Because C, although the syntax is more complex, provides underlying control capabilities and performance advantages. 1. In terms of syntax structure, C uses curly braces {} instead of indentation to organize code blocks, and variable types must be explicitly declared; 2. In terms of type system and memory management, C does not have an automatic garbage collection mechanism, and needs to manually manage memory and pay attention to releasing resources. RAII technology can assist resource management; 3. In functions and class definitions, C needs to explicitly access modifiers, constructors and destructors, and supports advanced functions such as operator overloading; 4. In terms of standard libraries, STL provides powerful containers and algorithms, but needs to adapt to generic programming ideas; 5

Polymorphisms in C are divided into runtime polymorphisms and compile-time polymorphisms. 1. Runtime polymorphism is implemented through virtual functions, allowing the correct method to be called dynamically at runtime. 2. Compilation-time polymorphism is implemented through function overloading and templates, providing higher performance and flexibility.

C polymorphismincludescompile-time,runtime,andtemplatepolymorphism.1)Compile-timepolymorphismusesfunctionandoperatoroverloadingforefficiency.2)Runtimepolymorphismemploysvirtualfunctionsforflexibility.3)Templatepolymorphismenablesgenericprogrammingfo

C polymorphismisuniqueduetoitscombinationofcompile-timeandruntimepolymorphism,allowingforbothefficiencyandflexibility.Toharnessitspowerstylishly:1)Usesmartpointerslikestd::unique_ptrformemorymanagement,2)Ensurebaseclasseshavevirtualdestructors,3)Emp
