First things first: printf is expecting a valid (i.e. non-NULL) pointer for its %s argument so passing it a NULL is officially undefined. It may print “(null)” or it may delete all files on your hard drive–either is correct behavior as far as ANSI is concerned (at least, that’s what Harbison and Steele tells me.)

https://stackoverflow.com/questions/11589342/what-is-the-behavior-of-printing-null-with-printfs-s-specifier/11589443#11589443

#programming #c #null

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

What I found out was that even though there are frustrating moments when inheritance IS actually the optimal solution, being forced to use composition has helped me think differently about how to structure my code for the better. Inheritance makes it too easy to design yourself into a trap where refactoring becomes extremely expensive even when necessary. Go is designed to make refactoring much easier by doing things like forcing the use of composition.

https://www.quora.com/Why-should-someone-choose-Go-as-his-main-programming-language

#golang #programming

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)