I don't know whether I am a typical user, but anyway:
What I expect from the Component Pascal Compiler
A Component Pascal Compiler. For Windows and Linux.
A linker which generates executables and libraries for Windows and Linux.
A garbage collector (no need to deallocate objects generated with NEW).
Some debugging facility, e.g. GDB or the trap viewer of the Component Builder.
Possibility of interface files / linking to C libraries.
As many directory levels as I want.
What I don't expect:
A complete development system with editor, window system and so on.
Automated build facility. Comands for the compilation of a single file and for
linking several files to one executable or library is enough. Automation can
be done by the user with shell scripts or the make facility.
Lots of libraries. Just In, Out, Math, not much more.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A Component Pascal Compiler. For Windows and Linux.
A linker which generates executables and libraries for Windows and Linux.
Of course. It's a main goal of a project.
A garbage collector (no need to deallocate objects generated with NEW).
Possibility of interface files / linking to C libraries.
These features are defined in Component Pascal language report, so must have
it.
Some debugging facility, e.g. GDB or the trap viewer of the Component
Builder.
Trap viewer is one of the features that I initially outlined for
implementation. Must have because of its importance. Need to work on concept
of trap viewer, because it interactive by origin (GUI), but a console doesn't
allow such interactiveness.
What I don't expect:
A complete development system with editor, window system and so on.
Sure. At least not at this stage.
Automated build facility.
Yes. It will be implemented later.
Lots of libraries. Just In, Out, Math, not much more.
Exactly. I'm working on implementation of basic set of libraries as you
pointed.
I don't know whether I am a typical user, but anyway:
A feedback from typical users is necessary and beneficial. It stimulates my
work on this project.
Thank you for pointing out the expectations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know whether I am a typical user, but anyway:
What I expect from the Component Pascal Compiler
A Component Pascal Compiler. For Windows and Linux.
A linker which generates executables and libraries for Windows and Linux.
A garbage collector (no need to deallocate objects generated with NEW).
Some debugging facility, e.g. GDB or the trap viewer of the Component Builder.
Possibility of interface files / linking to C libraries.
As many directory levels as I want.
What I don't expect:
A complete development system with editor, window system and so on.
Automated build facility. Comands for the compilation of a single file and for
linking several files to one executable or library is enough. Automation can
be done by the user with shell scripts or the make facility.
Lots of libraries. Just In, Out, Math, not much more.
Of course. It's a main goal of a project.
These features are defined in Component Pascal language report, so must have
it.
Trap viewer is one of the features that I initially outlined for
implementation. Must have because of its importance. Need to work on concept
of trap viewer, because it interactive by origin (GUI), but a console doesn't
allow such interactiveness.
Sure. At least not at this stage.
Yes. It will be implemented later.
Exactly. I'm working on implementation of basic set of libraries as you
pointed.
A feedback from typical users is necessary and beneficial. It stimulates my
work on this project.
Thank you for pointing out the expectations.