Feb.18.1996
I had played with the Development Assistant and it seemed to be a very useful tool. I have steel some quotation about the ability of the tools to deal with our project.
The software development for the project is a very complicated process (100MB of sources and 2.5MB of code). The system software is distributed over several hardware platforms. Features are developed by many software engineers and then integrated to one software version.
1. The language is Intel Cx86 with procedure name with $ e.g., rq$send$message.
We have tested with a large project: ANSI C 17.5MB source code under Windows 3.1, 95 and NT. Now one 95 or NT is available. It is 40-50% faster. I think it is very good for your very large project. The procedure names shall not be a problem.
2. The OS is Intel RMX x.86 on PC based machine.
DAC is only for Windows available.
3. There are some call gates written in ASM.
The ASM would not be parsed but there are corresponding *.h files with a useful data or the following possibility:
From Development Assistant for C manual:
The C language extensions used in C dialects supported by SourceMode parameter and listed in Options/Analysis dialog are normally handled by the source analysis.
If the analyzed source contains some unsupported extensions, they can be handled by defining of suitable preprocessor macros. For example, a macro which replaces a special storage class specifier with nothing, could be set in the Defines segment of the Options/Analysis dialog.
Another way is customization of analyzed source for Development Assistant for C by usage of __DA_C__ macro identifier. For example, Development Assistant for C does not recognize the use of symbols within assembler statements or blocks, and generates a warning when asm, _asm or _asm statement is used. This can be solved by:
#ifndef __DA_C__
asm { mov x,4; mov bx,dummy; }
#else x=4;
dummy;
#endif
4. There are old modules with PL/M-86 code.
We have one "Development Assistant for PL/M" also. The C and PL/M source CAN'T be mixed in a project but you can start one Development Assistant for C instance and one Development Assistant for PL/M instance. The rest of the project would be seen like a library respective.
5. Can you have net version and How match it cost.
Prices include free upgrades and support within 6 months of purchase. We have net version also. The prices depend on license count.
6. Can it work with the Codewright editor instead of your internal one?
Our editor has many connections to the rest of application (Browse, Graph). It is not possible to replace it with any other editor. You can start your own editor from a Tool-Bar for a active file in Development Assistant for C editor with a line number parameter (User Defined Actions macro language). You can reconfigure Development Assistant for C editor for your needs with Editor Macro Language. We would help you in doing it.
| * The present FAQ section is for DA-C V3.5. The FAQ section for DAC V4.x will be published soon. |
|
