Hey my programming friends, I have a question. My daughter is taking a C class in college and is using CLion to write her stuff. One of the comments her professor keeps saying is “remember to work in a Unix environment.”
I’ve always used an IDE when I program so I’m not sure what that means. Anyone able to help?
The article presents bfs, a tool written in C, to find files in a file system, like find or fd. It uses a breadth-first approach. It appears to be pretty effective in practise for the usecase described by the author of the article, which is also the author of the tool.
The benchmark is not well-designed and focus on one use case, but it opens doors for other tools to improve.
#c#clang
If your #C library function doesn't mutate memory passed to it but wants to return modifiable pointers, do you const the parameter but cast-away the const on return?
Or do you not const the parameter at all?
When moving to a compiler like #tcc from #gcc and #clang , what speed pitfalls should I be aware of that optimizations in those compilers typically hold our hand with, but tcc does not?
I've always used #swig to create #perl interfaces to #clang#c , but I noticed there is a #metacpan package Platypus that is a wrapper over libffi.
Any comparative experience?
#clang#ld#linker question: If I create a dylib libD.dylib that links against static libS.a, by default libD will contain a copy of all (referenced) symbols from S, and any users of libD would not need to link S to get all their needed symbols.
The problem comes along if there’s another dylib libE.dylib that also links against static libS.a. An executable that loads both libD and libE will now get duplicated symbols from S. Anything that should be globally unique in S will no longer be unique; there will be two copies of them.
Is there a way to make ld not include a copy of S in D and E (i.e. leave D’s and E’s references to symbols in S as unresolved externals)? It’s OK that users of D need to also link S; I want to make sure that there’s only one copy of the contents of S in the final executable.
The obvious answer is to turn S into a dylib as well, but I want to know if there’s actually a way to do what I want.
> The yank(1) utility reads input from stdin and display a selection interface that allows a field to be selected and copied to the clipboard. Fields are either recognized by a regular expression using the -g option or by splitting the input on a delimiter sequence using the -d option.
Are there any #llvm contributors/reviewers on here? I'm making some changes to improve Windows (CodeView) debug info and would love for someone to have a look. First change is here: https://reviews.llvm.org/D148761 #rust#clang
Why are people stuck in the ANSI #C standard from 1989 when writing new code ?
Even if one does not want to go full 21st century, numerous features that were introduced with the 1999 ISO C standard could make life a lot easier for professionals & hobbyists alike #clang#programming
Exploiting null Dereferences in the Linux Kernel | Project Zero (googleprojectzero.blogspot.com)