summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author balr0g <balrog032@gmail.com>2016-03-16 01:55:11 -0400
committer balr0g <balrog032@gmail.com>2016-03-16 01:55:11 -0400
commiteaed2fb593e34a0b67597a1e1a0de9148f9e20b3 (patch)
tree1ef03601dcff160b5a90134a3adb805cc6dff7c5
parent7c5bbfdf66e0fc87fa8f88b8891d901b96923d20 (diff)
Do not sort Doxygen member functions and macros for now (nw)
-rw-r--r--doxygen/doxygen.config2
1 files changed, 1 insertions, 1 deletions
diff --git a/doxygen/doxygen.config b/doxygen/doxygen.config
index c78081f9f05..d7115e0ef71 100644
--- a/doxygen/doxygen.config
+++ b/doxygen/doxygen.config
@@ -517,7 +517,7 @@ INLINE_INFO = YES
# name. If set to NO the members will appear in declaration order.
# The default value is: YES.
-SORT_MEMBER_DOCS = YES
+SORT_MEMBER_DOCS = NO
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
# descriptions of file, namespace and class members alphabetically by member
pan='5' class='logmsg'> LinkSupportCircularDependencies flag option (nw) * Fix OS X build on older Xcode versions (nw) AJR2020-06-181-0/+10 | * Enable option to generate symbols in Release as well as Debug under Visual ↵ Frank Palazzolo2020-05-271-0/+5 | | | | Studio. (This is important because debugging Debug builds is too slow) * mingw: get rid of missing end-group warning (nw) hap2020-05-101-2/+2 | * GCC 10 fix for sqlite3 (nw) arbee2020-05-021-0/+5 | * Fix hang with Emscripten's "upstream" backend (nw) Justin Kerk2020-04-161-0/+2 | * removed the remaining bits of the FASTDEBUG/MAME_DEBUG_FAST silliness I ↵ firewave2020-01-211-16/+0 | | | | introduced ages ago (nw) * Lower number of warnings disabled with visual studio from 71 to 27 (nw) yz70s2020-01-021-58/+16 | | | | | And most of the remaining ones could be removed with simple code modifications. * Revert "Revert "enable clang missing braces warning - it's useful to be able ↵ Vas Crabb2019-12-211-1/+0 | | | | | | to see when you're initialising a structure or nested array inside an array"" This reverts commit 4264fcd1369dadbb774fd681bf9375e2761d5286. * Revert "enable clang missing braces warning - it's useful to be able to see ↵ AJR2019-12-201-0/+1 | | | | | | when you're initialising a structure or nested array inside an array" This (mostly) reverts commit 6959de07197e623262e614fdd0734007a41eb778. * enable clang missing braces warning - it's useful to be able to see when ↵ Vas Crabb2019-12-201-1/+0 | | | | you're initialising a structure or nested array inside an array * damn inconsistent macros, maybe I really _will_ kill them off next year (nw) Vas Crabb2019-12-201-2/+2 | * Enable visual studio warning C5038 about member initialization order (nw) yz70s2019-12-201-14/+13 | | | | Also put vs warning options all in one place. * Revert "Fix gcc version 5 compile. (nw)" couriersud2019-11-011-10/+4 | | | | This reverts commit b1246642eb6e3f48f1fe19b7ae6584c1e544e88b. * Fix gcc version 5 compile. (nw) couriersud2019-11-011-4/+10 | | | | Cross compiling for windows on certain ubuntu versions fails without this. * Make devdelegate more like devcb for configuration. This is a Vas Crabb2019-10-261-10/+4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fundamental change to show device delegates are configured. Device delegates are now aware of the current device during configuration and will resolve string tags relative to it. This means that device delegates need a device to be supplied on construction so they can find the machine configuration object. There's a one-dimensional array helper to make it easier to construct arrays of device delegates with the same owner. (I didn't make an n-dimensional one because I didn't hit a use case, but it would be a simple addition.) There's no more bind_relative_to member - just call resolve() like you would for a devcb. There's also no need to cast nullptr when creating a late bind device delegate. The flip side is that for an overloaded or non-capturing lambda you'll need to cast to the desired type. There is one less conditional branch in the hot path for calls for delegates bound to a function pointer of member function pointer. This comes at the cost of one additional unconditional branch in the hot path for calls to delegates bound to functoids (lambdas, functions that don't take an object reference, other callable objects). This applies to all delegates, not just device delegates. Address spaces will now print an error message if a late bind error is encountered while installing a handler. This will give the range and address range, hopefully making it easier to guess which memory map is faulty. For the simple case of allowing a device_delegate member to be configured, use a member like this: template <typename... T> void set_foo(T &&...args) { m_foo_cb.set(std::forward<T>(args)...); } For a case where different delegates need to be used depending on the function signature, see src/emu/screen.h (the screen update function setters). Device delegates now take a target specification and function pointer. The target may be: * Target omitted, implying the current device being configured. This can only be used during configuration. It will work as long as the current device is not removed/replaced. * A tag string relative to the current device being configured. This can only be used during configuration. It will not be callable until .resolve() is called. It will work as long as the current device is not removed/replaced. * A device finder (required_device/optional_device). The delegate will late bind to the current target of the device finder. It will not be callable until .resolve() is called. It will work properly if the target device is replaced, as long as the device finder's base object isn't removed/replaced. * A reference to an object. It will be callable immediately. It will work as long as the target object is not removed/replaced. The target types and restrictions are pretty similar to what you already have on object finders and devcb, so it shouldn't cause any surprises. Note that dereferencing a device finder will changes the effect. To illustrate this: ... required_device<some_device> m_dev; ... m_dev(*this, "dev") ... // will late bind to "dev" relative to *this // will work if "dev" hasn't been created yet or is replaced later // won't work if *this is removed/replaced // won't be callable until resolve() is called cb1.set(m_dev, FUNC(some_device::w)); ... // will bind to current target of m_dev // will not work if m_dev is not resolved // will not work if "dev" is replaced later // will be callable immediately cb2.set(*m_dev, FUNC(some_device::w)); ... The order of the target and name has been reversed for functoids (lambdas and other callable objects). This allows the NAME macro to be used on lambdas and functoids. For example: foo.set_something(NAME([this] (u8 data) { m_something = data; })); I realise the diagnostic messages get ugly if you use NAME on a large lambda. You can still give a literal name, you just have to place it after the lambda rather than before. This is uglier, but it's intentional. I'm trying to drive developers away from a certain style. While it's nice that you can put half the driver code in the memory map, it detracts from readability. It's hard to visualise the memory range mappings if the memory map functions are punctuated by large lambdas. There's also slightly higher overhead for calling a delegate bound to a functoid. If the code is prettier for trivial lambdas but uglier for non-trivial lambdas in address maps, it will hopefully steer people away from putting non-trivial lambdas in memory maps. There were some devices that were converted from using plain delegates without adding bind_relative_to calls. I fixed some of them (e.g. LaserDisc) but I probably missed some. These will likely crash on unresolved delegate calls. There are some devices that reset delegates at configuration complete or start time, preventing them from being set up during configuration (e.g. src/devices/video/ppu2c0x.cpp and src/devices/machine/68307.cpp). This goes against the design principles of how device delegates should be used, but I didn't change them because I don't trust myself to find all the places they're used. I've definitely broken some stuff with this (I know about asterix), so report issues and bear with me until I get it all fixed. * Fix build for nonstandard compiler versions like '8.3-win32'