c
Productivity
file annotation
SHOW HN2012
How HN took it
5 positive, 13 neutral or asking, 0 mixed, 11 critical, out of 29 comments about the project. Thread score -0.09.
Idea: 4 for, 1 againstExecution: 0 for, 3 againstDesign: 0 for, 3 againstDocs: 0 for, 1 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
Good learning project and useful feedback
From 2 comments
I love this post and the exchange of comments going on here. The OP is just starting to learn C, and to help learn it got started on a project that they found useful, which I…
mfonda on HNAs a sub-novice C/++ programmer myself, it's awesome to see a program like this being discussed. The source code is relatively short, it's a simple enough implementation, and all…
azelfrath on HN
Useful idea
From 2 comments
Great idea - I think 'c' should be a shell alias though. Tagging support would be cool.
gouranga on HNThis is really cool! Thanks for sharing.
swordswinger12 on HN
Hidden-file comment storage is a handy feature, like 4DOS
From 1 comment
4DOS used to have this. It was especially useful back in the day with the 8.3 DOS filenames, which often weren't very descriptive. It's nice to see this feature return.
zephyrfalcon on HN
Objections
Name 'c' is a bad name and conflicts with others
From 2 comments
Terrible, terrible name.
davyjones on HNAre you sure you committed it to the homebrew repository on github? Your github page doesn't show any activity that indicates you've forked the homebrew repo or created a pull…
mjschultz on HN
Homebrew install suggestion is a bad idea
From 2 comments
``` And those on Mac should be able to use: $ brew install c ``` Wow, uh, didn't it strike you that this might be a bad idea?
redbad on HNAs far as I can tell, this program is not included in Homebrew.
sharth on HN
Code has memory and error handling problems
From 2 comments
Comments for your C learning: ``` #include <stdbool.h> ``` is better than ``` typedef int bool; #define true 1 #define false 0 ``` Always, always, surround your if and else…
leif on HNI see 17 mallocs and not one free!
databus on HN
Comments stored in hidden dotfiles is messy
From 2 comments
I'd prefer to have all the comments located in a single location (e.g. ~/.comments or ~/Dropbox/comments-<hostname>) rather than litter hidden files all over the place because I…
brimpa on HNHidden files are handy for some things, but a README.txt file would be apparent to anybody who comes across the directory, and not just someone who knows that the hidden…
jcromartie on HN
Requests
Store comments in extended file attributes
From 2 comments
It may be more appropriate to store the comments in extended attributes rather than in dotfiles: http://en.wikipedia.org/wiki/Extended_file_attributes
markdrago on HNWouldn't it be better to use Extended file attributes ? https://gist.github.com/2695264 (actually my first attempt to a bash script)
ga2arch on HN
Add tagging support
From 1 comment
Great idea - I think 'c' should be a shell alias though. Tagging support would be cool.
gouranga on HN
Store all comments in one location
From 1 comment
I'd prefer to have all the comments located in a single location (e.g. ~/.comments or ~/Dropbox/comments-<hostname>) rather than litter hidden files all over the place because I…
brimpa on HN
Add a README so the feature is discoverable
From 1 comment
Hidden files are handy for some things, but a README.txt file would be apparent to anybody who comes across the directory, and not just someone who knows that the hidden…
jcromartie on HN
Questions
Why use autoconf
From 1 comment
Why did you decide to use autoconf?
mccoyst on HN
Why use getcwd this way instead of an if check
From 1 comment
``` if (getcwd(cwd, sizeof(cwd)) != NULL) ; else perror("getcwd() error"); ``` Is that common? What's the advantages over the below? ``` if (... == NULL) { perror(...); } ```
ajanuary on HN
Alternatives named
Extended file attributes
From 2 comments
It may be more appropriate to store the comments in extended attributes rather than in dotfiles: http://en.wikipedia.org/wiki/Extended_file_attributes
markdrago on HNWouldn't it be better to use Extended file attributes ? https://gist.github.com/2695264 (actually my first attempt to a bash script)
ga2arch on HN
4DOS
From 1 comment
4DOS used to have this. It was especially useful back in the day with the 8.3 DOS filenames, which often weren't very descriptive. It's nice to see this feature return.
zephyrfalcon on HN