phoppermann
phoppermann
@rodneyp290 yes, it works normally. However, the include syntax with `` suggests that it's a system include (which is not the case here). See also https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html. Apart from theoretical considerations,...
> I think the use of is the right one. Open DIS is a library that will get installed on the system e.g. /usr/local/include/dis6/Acknowledge.h. Then in your app you would...
`#pragma once` would be fine for me as well. @leif81 what do you think? This should be implemented in xmlpg as well.
@rodneyp290 could you change your script to use `#pragma once`?
Compare e.g. https://github.com/lunarmodules/luafilesystem/blob/ff2cbc21f1a2fd34d30c0840ff2abb0121d46131/src/lfs.h#L34. This is required if you want to compile as C++ (not C), otherwise the symbols are not found in `require`. This has been advised for Lua itself...
>Instead I believe you have to include the entire lua header(s) inside of an extern "C". > >Lua modules such as luasocket should similarly be included inside of an extern...
> For instance, when requiring a.b.c, it will search for a C library for a. If found, it looks into it for an open function for the submodule; in our...
Well, I've encountered the issue when `require` luasocket as is from C++ Lua. If you tell me that this cannot happen because the module loader doesn't care about C/C++, I...
Also as C++ (like Lua itself to be aligned). Maybe that's not the right way?