Ruby
3.4.0dev (2024-11-05 revision 348a53415339076afc4a02fcd09f3ae36e9c4c61)
|
Go to the source code of this file.
Macros | |
#define | _(args) () |
This was a transition path from K&R to ANSI. More... | |
#define | __(args) () |
This was a transition path from K&R to ANSI. More... | |
#define | ANYARGS ... |
Functions declared using this macro take arbitrary arguments, including void. More... | |
Defines old _.
RBIMPL
or rbimpl
are implementation details. Don't take them as canon. They could rapidly appear then vanish. The name (path) of this header file is also an implementation detail. Do not expect it to persist at the place it is now. Developers are free to move it anywhere anytime at will. __VA_ARGS__
is always available. We assume C99 for ruby itself but we don't assume languages of extension libraries. They could be written in C++98.Nobody should ever use these macros any longer. No known compilers lack prototypes today. It's 21st century. Just forget them.
Definition in file stdarg.h.
#define _ | ( | args | ) | () |
This was a transition path from K&R to ANSI.
#define __ | ( | args | ) | () |
This was a transition path from K&R to ANSI.
#define ANYARGS ... |
Functions declared using this macro take arbitrary arguments, including void.
This was a necessary evil when there was no such thing like function overloading. But it is the 21st century today. People generally need not use this. Just use a granular typed function.