Dec.02.1995
We do have some comments and questions. Our development environment uses MS-Visual C++ compiler and GNU 2.60 compilers, our own makefile builder, gnu-make, Editor, and RCS tools which reside on both the SUNs and MS-DOS machines. All the machines are mounted to a common RCS database where our software revisions are stored. Since we have a great deal of knowledge of compilers and configurations management, it is important that a tool (I call them HLDE - high level design environment tools) integrate with these existing tools. We expect to remove tools like Editor if it does not fit appropriately. It is important that our existing configuration management tools be kept intact.
We have attempted to integrate tools like Hindsight and McCabe's tools without much success.
We have worked with care to allow you not to change your existing development environment. You can execute any compiler or make or any other program and automatically use its output in Development Assistant for C. Chances are that you will stop using your editor because our has more possibilities.
Our editor is specially adjusted for C and it is not designed to be used for other languages, we will produce different dac for them with their own adjustments. It would be practically impossible to put all languages in only one package, especially if you would have to configure package for all of them. We support various dialects of C, but you can not redefine Development Assistant for C to support additional languages. Keyboard bindings are implanted, but user can change and redefine them.
In Development Assistant for C graph always starts from chosen node because practice showed no sense in displaying monstrous graphs. Instead, you are always interested in a given function and its direct neighborhood. In Development Assistant for C you can define level of recursive displaying of graph.
We hope these answers helped you to get realistic picture of our software and that you will contact us again if you want further discussion on these or any new questions.
| * The present FAQ section is for DA-C V3.5. The FAQ section for DAC V4.x will be published soon. |
|
