News for hackers. Stuff that matters.
Re:F() vs. F(void) in C vs. C++ by Gibbon1 on Sunday May 12, 2019 @07:23PM (#19895264)
What I would like in C is a way to specify an argument list. And be able to slop them around and call functions with them later.

So perhaps foo(args) means foo takes a list of arguments unspecified.

Re:F() vs. F(void) in C vs. C++ by nitrogen on Sunday May 12, 2019 @11:42PM (#19896289)
You can approximate an argument list using compound literals as long as 0/NULL is an acceptable default value. It's a bit noisy, but it works something like this if I remember right:

    result = foo(&(struct foo_args){.arg1 = 4, .arg7 = "2"})
Re:F() vs. F(void) in C vs. C++ by ndesaulniers on Monday May 13, 2019 @03:19AM (#19896957)
Re:F() vs. F(void) in C vs. C++ by kazinator on Monday May 13, 2019 @02:15PM (#19902092)
There are libraries for this like GNU ffcall and libffi.
Re:F() vs. F(void) in C vs. C++ by Gibbon1 on Monday May 13, 2019 @03:01PM (#19902691)
Looked at those. Problem with libffi is it wasn't ported to a 32 bit arm. And the interface is 'clunkie'

I think what I want is llvm's blocks. Which isn't available in gcc.

Re:F() vs. F(void) in C vs. C++ by unilynx on Monday May 13, 2019 @03:10AM (#19896915)
Like va_list in vprintf ?