c语言精通经典语录(c语言修仙经典语录)

c语言精通至少10年，不是危言耸听！？c语言博大精深，想精通c语

如果只是想编一些一般的程序那用不了这么长的时间，如果想成为这门语言的大神级人物，10年……未够吧。深入的学习一门编程语言，必须要学习计算机原理吧。你说你学了C语言，连汇编都不会你好意思出门么。把这些都学会，能运用自如只能算你学会了，还要有独特的创意和灵感才能说是精通了。反正我是不考虑了，人懒，没戏了。

一般几年可以精通C语言

要是纯粹从语言角度来说的话，几个月的时间就可以把c语言完全掌握了

但是，你学会语言是要用来编写程序的，这就需要你学习大量的软件设计，操作系统，数据结构等等相关知识了，并且在大量实践中掌握大量开发经验，这些都学好怎么也得三五年时间

有哪些和编程有关的经典语句

2. One man's constant is another man's variable.

3. Functions delay binding: data structures induce binding. Moral: Structure data late in the programming process.

4. Syntactic sugar causes cancer of the semi-colons.

5. Every program is a part of some other program and rarely fits.

6. If a program manipulates a large amount of data, it does so in a small number of ways.

7. Symmetry is a complexity reducing concept (co-routines include sub-routines); seek it everywhere.

8. It is easier to write an incorrect program than understand a correct one.

9. A programming language is low level when its programs require attention to the irrelevant.

10. It is better to have 100 functions operate on one data structure than 10 functions on 10 data structures.

11. Get

into a rut early: Do the same processes the same way. Accumulate

idioms. Standardize. The only difference (!) between Shakespeare and you

was the size of his idiom list - not the size of his vocabulary.

12. If you have a procedure with 10 parameters, you probably missed some.

13. Recursion is the root of computation since it trades description for time.

14. If two people write exactly the same program, each should be put in micro-code and then they certainly won't be the same.

15. In the long run every program becomes rococo - then rubble.

16. Everything should be built top-down, except the first time.

17. Every program has (at least) two purposes: the one for which it was written and another for which it wasn't.

18. If a listener nods his head when you're explaining your program, wake him up.

19. A program without a loop and a structured variable isn't worth writing.

20. A language that doesn't affect the way you think about programming, is not worth knowing.

21. Wherever

there is modularity there is the potential for misunderstanding: Hiding

information implies a need to check communication.

22. Optimization hinders evolution.

23. A good system can't have a weak command language.

24. To understand a program you must become both the machine and the program.

25. Perhaps if we wrote programs from childhood on, as adults we'd be able to read them.

26. One

can only display complex information in the mind. Like seeing, movement

or flow or alteration of view is more important than the static

picture, no matter how lovely.

27. There will always be things we wish to say in our programs that in all known languages can only be said poorly.

28. Once you understand how to write a program get someone else to write it.

29. Around

computers it is difficult to find the correct unit of time to measure

progress. Some cathedrals took a century to complete. Can you imagine

the grandeur and scope of a program that would take as long?

30. For

systems, the analogue of a face-lift is to add to the control graph an

edge that creates a cycle, not just an additional node.

31. In programming, everything we do is a special case of something more general - and often we know it too quickly.

32. Simplicity does not precede complexity, but follows it.

33. Programmers are not to be measured by their ingenuity and their logic but by the completeness of their case analysis.

34. The 11th commandment was "Thou Shalt Compute" or "Thou Shalt Not Compute" - I forget which.

35. The

string is a stark data structure and everywhere it is passed there is

much duplication of process. It is a perfect vehicle for hiding

information.

36. Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers.

37. The

use of a program to prove the 4-color theorem will not change

mathematics - it merely demonstrates that the theorem, a challenge for a

century, is probably not important to mathematics.

38. The

most important computer is the one that rages in our skulls and ever

seeks that satisfactory external emulator. The standardization of real

computers would be a disaster - and so it probably won't happen.

39. Structured Programming supports the law of the excluded muddle.

40. Re

graphics: A picture is worth 10K words - but only those to describe the

picture. Hardly any sets of 10K words can be adequately described with

pictures.

41. There are two ways to write error-free programs; only the third one works.

42. Some programming languages manage to absorb change, but withstand progress.

43. You can measure a programmer's perspective by noting his attitude on the continuing vitality of FORTRAN.

44. In software systems it is often the early bird that makes the worm.

45. Sometimes I think the only universal in the computing field is the fetch-execute-cycle.

46. The goal of computation is the emulation of our synthetic abilities, not the understanding of our analytic ones.

47. Like punning, programming is a play on words.

48. As Will Rogers would have said, "There is no such thing as a free variable."

49. The

best book on programming for the layman is "Alice in Wonderland"; but

that's because it's the best book on anything for the layman.

50. Giving

up on assembly language was the apple in our Garden of Eden: Languages

whose use squanders machine cycles are sinful. The LISP machine now

permits LISP programmers to abandon bra and fig-leaf.

51. When we understand knowledge-based systems, it will be as before - except our finger-tips will have been singed.

52. Bringing computers into the home won't change either one, but may revitalize the corner saloon.

53. Systems have sub-systems and sub-systems have sub-systems and so on ad infinitum - which is why we're always starting over.

54. So many good ideas are never heard from again once they embark in a voyage on the semantic gulf.

55. Beware of the Turing tar-pit in which everything is possible but nothing of interest is easy.

56. A LISP programmer knows the value of everything, but the cost of nothing.

57. Software is under a constant tension. Being symbolic it is arbitrarily perfectible; but also it is arbitrarily changeable.

58. It is easier to change the specification to fit the program than vice versa.

59. Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.

60. In English every word can be verbed. Would that it were so in our programming languages.

61. Dana Scott is the Church of the Lattice-Way Saints.

62. In programming, as in everything else, to be in error is to be reborn.

63. In computing, invariants are ephemeral.

64. When we write programs that "learn", it turns out we do and they don't.

65. Often it is means that justify ends: Goals advance technique and technique survives even when goal structures crumble.

66. Make

no mistake about it: Computers process numbers - not symbols. We

measure our understanding (and control) by the extent to which we can

arithmetize an activity.

67. Making something variable is easy. Controlling duration of constancy is the trick.

68. Think of all the psychic energy expended in seeking a fundamental distinction between "algorithm" and "program".

69. If

we believe in data structures, we must believe in independent (hence

simultaneous) processing. For why else would we collect items within a

structure? Why do we tolerate languages that give us the one without the

other?

70. In a 5 year period we get one superb programming language. Only we can't control when the 5 year period will begin.

71. Over

the centuries the Indians developed sign language for communicating

phenomena of interest. Programmers from different tribes (FORTRAN, LISP,

ALGOL, SNOBOL, etc.) could use one that doesn't require them to carry a

blackboard on their ponies.

72. Documentation is like term insurance: It satisfies because almost no one who subscribes to it depends on its benefits.

73. An adequate bootstrap is a contradiction in terms.

74. It

is not a language's weaknesses but its strengths that control the

gradient of its change: Alas, a language never escapes its embryonic

75. It is possible that software is not like anything

else, that it is meant to be discarded: that the whole point is to

always see it as soap bubble?

76. Because of its vitality, the computing field is always in desperate need of new cliches: Banality soothes our nerves.

77. It is the user who should parameterize procedures, not their creators.

78. The

cybernetic exchange between man, computer and algorithm is like a game

of musical chairs: The frantic search for balance always leaves one of

the three standing ill at ease.

79.如果你对c语言感兴趣，这是好事情。c语言确实可以做很多事情。 网络上面已经有不少关于c语言的学习文章了。 你可以百度一下， 80x86汇编小站， 看看 站长写的下面这几篇关于c语言编程的文章， 或者 你直接联系 这个站长 跟他交流编程方面的事情

c.c经典语句？