Autodesk / Autodesk/AutomaticComponentToolkit
[C++] Interfacewrapper.cpp compilation failure (string cache)
- 主要语言
- Go
- 星标
- 53
- 派生
- 26
- PR 合并指标
- 30 天内没有已合并 PR
描述
Given a function with a class / optionalclass argument, the generated code ends up looking something like this:
interfacewrapper.cpp
```c++
std::string sName("");
IBase* pBaseThisResult(nullptr);
IFoo* pIFoo = dynamic_cast(pIBaseClass);
if (!pIFoo)
throw EMyComponentInterfaceException(MYCOMPONENT_ERROR_INVALIDCAST);
bool isCacheCall = (pNameBuffer == nullptr);
if (isCacheCall) {
pBaseThisResult = pIFoo->GetProperties(sName, *pBar);
pIFoo->_setCache (new ParameterCache_3 (sName, *pBar, pBaseThisResult));
}
else {
auto cache = dynamic_cast*> (pIFoo->_getCache ());
if (cache == nullptr)
throw EMyComponentInterfaceException(MYCOMPONENT_ERROR_INVALIDCAST);
cache->retrieveData (sName, *pBar, pBaseThisResult);
pIFoo->_setCache (nullptr);
}
```
Since ` CMyComponentFoo` is a binding class, this won't compile. Also, the pointer `pBaseThisResult` is actually of type `IBase *`.
I've hacked a fix to get it to work by generating `IBase *` instead, but as I don't know how this parameter caching is supposed to work I can't say if it's the right way to fix it.
贡献指南
调研方向
Start with the generated interfacewrapper.cpp example and inspect how parameter caching handles class or optionalclass arguments. Trace the types used for pBaseThisResult, ParameterCache_3, and the binding class CMyComponentFoo, then verify the generated wrapper compiles and that the cache path still behaves correctly.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- cpp
- 领域
- tooling
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100