Hi, I wanted to follow up on a post I provided in December which was:AST C++ support and the cstdio header. After debugging a core dump, I noticed the stack trace was very different when cstdio is included vs stdio.h. When a code module uses only stdio.h (the code is focused more on C) I see there is some translation of the IO functions to "__ast_" versions. I am sure this is to properly control I/O within the shell command environment. But when I use cstdio no such translations happen (I assume the issue is related to the namespace "std"). It was easy to verify this with nm as this is what I would see when things worked correctly for example:
U _ast_fprintf U _ast_printf So my main question is, does the AST ksh built-in really fully support C++? I noticed many of the notes on doing built-ins reference the C++ compiler which seems to work fine. But I assume there are some limitations with broad C++ implementations (especially with regard to using cstdio). If the simple answer is that any C++ integration should be somewhat rudimentary to work with AST, then perhaps you could list more details about this in the docs which walk through building built-in commands (man pages, etc). Or at least touch on any limitations to cstdio capabilities. I was unable to find specifics on this looking around the Web or within some of the archive notes. Thanks in advance for your kind assistance. Doug..
_______________________________________________ ast-users mailing list ast-users@lists.research.att.com http://lists.research.att.com/mailman/listinfo/ast-users
