Graph-Reply
Data
graph database
SHOW HN2015
How HN took it
2 positive, 2 neutral or asking, 0 mixed, 1 critical, out of 5 comments about the project. Thread score 0.00.
Execution: 1 for, 1 againstIdea: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Commenters call the project neat and encourage continued C learning
From 2 comments
Some general feedback: In C you separate your implementation from your interface with header files. If you include .c files in .c files it will end up causing a lot of problems…
jotux on HNAs well as jotux's excellent reply, I'd like to add that clint, valgrind and friends help out a lot when starting out with C. Learning to use these tools well (by using them all…
_sh on HN
Objections
Multiple C safety issues: memory leaks, fixed-size sscanf buffers, unsafe input handling
From 2 comments
I do a lot of embedded C, so I generally avoid dynamically allocating memory, but when I do the way I try to avoid memory leaks is to always try to allocate and free in the same…
jotux on HNC is not a safe language sort of by definition, so you always have to consider all the possibilities. For example, you use sscanf in places, with fixed sized buffers. What…
axoltl on HN
Includes .c files instead of using header files, making include order matter
From 1 comment
Some general feedback: In C you separate your implementation from your interface with header files. If you include .c files in .c files it will end up causing a lot of problems…
jotux on HN
Code produces compiler warnings; use -Wall
From 1 comment
Some general feedback: In C you separate your implementation from your interface with header files. If you include .c files in .c files it will end up causing a lot of problems…
jotux on HN
Requests
Restructure memory allocation so malloc and free share a scope
From 1 comment
I do a lot of embedded C, so I generally avoid dynamically allocating memory, but when I do the way I try to avoid memory leaks is to always try to allocate and free in the same…
jotux on HN
Use header files per source file
From 1 comment
Some general feedback: In C you separate your implementation from your interface with header files. If you include .c files in .c files it will end up causing a lot of problems…
jotux on HN
Alternatives named
valgrind and clint for C memory debugging
From 1 comment
As well as jotux's excellent reply, I'd like to add that clint, valgrind and friends help out a lot when starting out with C. Learning to use these tools well (by using them all…
_sh on HN
JPL C coding standard
From 1 comment
I do a lot of embedded C, so I generally avoid dynamically allocating memory, but when I do the way I try to avoid memory leaks is to always try to allocate and free in the same…
jotux on HN