Skip to content
quotesby

About this quote

What does it mean?
The author calls including a non‑standard header a fatal error and labels it bad language design.
In plain terms
Including a header that isn’t universally available is a serious design flaw.
What can you take from it?
Avoid dependencies that break on some systems.

Where it applies

  • cross‑platform development
  • library design

Putting it to work

  • provide fallback implementations
  • document required dependencies

Questions to consider

  • What strategies improve cross‑platform compatibility?
  • How to handle missing optional components?

Another view

Strict dependencies limit adoption on diverse platforms.

More from Larry Wall

  1. All language designers are arrogant. Goes with the territory... :-)

    Permalink to quote #28
  2. Besides, it's good to force C programmers to use the toolbox occasionally. :-)

    Permalink to quote #30
  3. You want it in one line? Does it have to fit in 80 columns? :-)

    Permalink to quote #27

Related quotes

  1. If you try to solve a hard problem, the question is not whether you will use a powerful enough language, but whether you will (a) use a powerful language, (b) …

    Paul GrahamPaul Graham quote #5
  2. Portability is for people who cannot write new programs.

    Linus TorvaldsLinus Torvalds quote #16
  3. All language designers are arrogant. Goes with the territory... :-)

    Larry WallLarry Wall quote #28