是否有替代品可以用来代替 iPhone SDK 中包含的 STL？
我目前正在使用 iPhone SDK 中包含的 STL。我无法在 Xcode 调试器中找到一种方法来查看列表、地图等中的数据，就像在 Visual Studio 中一样。在 Visual Studio 中，我可以遍历数据结构并查看列表、地图等中的数据。在 Xcode 中，这似乎不以相同的方式工作。我做错了什么吗？
I am currently using the STL included with the iPhone SDK. I haven't been able to find a way in the Xcode debugger to look at data that is in a list, map, etc. like I can within Visual Studio. Within Visual Studio, I can walk through the data structure and look at the data within the list, map, etc. Within Xcode, this doesn't seem to work the same way. Am I doing something wrong?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在我的 xcode 版本中，调试器中似乎对容器有一些支持 - 我正在运行从操作系统磁盘安装的 3.2，当我创建向量类时，我可以浏览它们的元素 - 它们看起来就像数组一样，尽管它可以并不总是处理向量内的向量，以及其他更复杂的场景。
我不太确定为什么它不适合您，但我建议您执行以下操作：
a) 确保您拥有最新版本的 xcode。
b）具体尝试向量类，我可以保证它在我的版本中工作 - 无论您是否想使用此类来帮助故障排除过程。
c) 尝试在全局级别使用向量，而不是在结构负载中缩进。
d) 如果它真的让你恼火，那么从安装磁盘上安装 xcode 可能会有所帮助（除非在下载 iPhone SDK 之前已经安装了 xcode）。我不确定是否存在差异，而且我认为没有任何意义（在另一个问题中询问社区可能是明智的）。
In my version of xcode there seems to be some support for containers in the debugger - I'm running 3.2 installed off my OS Disk and when I make vector classes I can browse through their elements - they appear just as arrays do, although it can't always handle a vector within a vector, and other more complex scenarios.
I'm not really to sure why its not working for you, but I would recommend the following:
a) Make sure you have the latest version of xcode available.
b) Try the vector class specifically, I can vouch for it working in my version - whether or not you want to use this class that'll help the troubleshooting process.
c) Try using the vector at global level rather then indented within loads of structures.
d) If its really irritating you then its possible installing xcode off your install disk would help (unless already had it previous to downloading the iPhone SDK). I'm not to sure if there is a difference, and I don't see the sense in there being any though (probably wise to ask the community in another question).