Quote:Original post by jantaHahaha now that is tempting.
For a good laugh, turn that function into a variadic one.
I just had a nice little chat with my boss and a coworker. My boss is all for using a struct/class, but my coworker isn't. He likes having a lot of parameters. He says it's like a shopping list. He also says there would be alignment issues between C and C++. But we're using C++ objects in the API (like std::string and std::vector)... how do I tell him that we aren't even targeting C? And as for possible alignment errors with C++, how do I combat him on that? Surely if there are alignment errors they'll show up in more than the struct we would be passing for that function? So why worry so much about that one struct that would simplify life so, so mch? And we're delivering libraries for all our targeted compilers and platforms, so that shouldn't be an issue. Someone give me some ammo for his alignment issues argument :)