<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[declareRunTimeSelectionTable在基类中可否同时调用两个？]]></title><description><![CDATA[<p dir="auto">各位前辈好，我最近准备从其他版本移植一个动网格功能时发现新旧版本之间motionSolver类在调用declareRunTimeSelectionTable函数时存在不同，旧版本中argList使用了Istream，新版本改为了Iodictionary。这导致旧版本的派生类移植到新版本遇到问题，如果直接改新版本的话又会导致其他派生类出现问题。因此可否在基类motionSolver中调用两次declareRunTimeSelectionTable，argList分别使用Istream和Iodictionary？<br />
事实上我在polyPatch.H中看到了调用两个declareRunTimeSelectionTable的例子：</p>
<pre><code>TypeName("patch");

    //- Debug switch to disallow the use of genericPolyPatch
    static int disallowGenericPolyPatch;


    // Declare run-time constructor selection tables

        declareRunTimeSelectionTable
        (
            autoPtr,
            polyPatch,
            word,
            (
                const word&amp; name,
                const label size,
                const label start,
                const label index,
                const polyBoundaryMesh&amp; bm,
                const word&amp; patchType
            ),
            (name, size, start, index, bm, patchType)
        );

        declareRunTimeSelectionTable
        (
            autoPtr,
            polyPatch,
            dictionary,
            (
                const word&amp; name,
                const dictionary&amp; dict,
                const label index,
                const polyBoundaryMesh&amp; bm,
                const word&amp; patchType
            ),
            (name, dict, index, bm, patchType)
        );
</code></pre>
<p dir="auto">但是不清楚是否是为了实现上述的功能？</p>
]]></description><link>https://cfd-china.com/topic/4340/declareruntimeselectiontable在基类中可否同时调用两个</link><generator>RSS for Node</generator><lastBuildDate>Sun, 16 Aug 2026 06:44:25 GMT</lastBuildDate><atom:link href="https://cfd-china.com/topic/4340.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 07 Dec 2020 07:16:07 GMT</pubDate><ttl>60</ttl></channel></rss>