Re: Ada OS

anon@xxxxxxxx (anon) writes:

That's one problem that I was also hinting at!

If a person manages an Ada project they should insure that each
version of the project works. And use documentation to info the user
how to make it work and states any known problems. Instead of just
finding an old project and dumping it into a CVS/SVN server.

There isn't a released C2Ada on sf.net.

"Simon Wright" should of archived the last Linux "c2ada" version
instead of posting the zip file contents, because it is easy to alter a
file and then post that altered file which can cause the project to
become non-functional.

"should *have*", please.

And it wasn't me, though it might have been. I'm a co-developer (& as
it happens admin) on the project, special interest in making it
portable (to Mac OS X, specifically).

Not sure where the last c2ada archive came from, only glad jcreem took
the initiative to make it visible so that interested parties can
contribute.

Plus, just dumping a broken project without the original package cause
the newbees to HATE Ada, because they can not use a project. And all
projects that are written in other languages should be only stored as
archived and re-written in Ada before posting the project. Because any
project that is written in standard Ada only language can be compiled
and executed by all. But if more than two languages are use most people
will just skip the project and move on.

If I was rewriting this project I would might not use Ada, but I would
certainly insist on a proper set of design documentation and code
standards. It's very difficult to gather what most of the subprograms
are for, what the pre- and post-conditions are etc, which makes it
very hard to change. Part of that's down to C and C habits, of course.

I think I would also abandon any attempt to make a generalised
translator, instead let's just (!) go for an interface generator.

Now, for the c2Ada, you should ask "Simon Wright" why he did
not insure that the c2ada project is full functional before he
posted it. Or have full documentation of how to build it.

You don't seem to understand what SourceForge is for!
.

Relevant Pages

  • Re: Ada OS
    ... Location of the main documentation and links ... If there is nothing in the download section then there is no release. ... the "c2ada" the program should be used on itself. ... Personally I wouldn't want to *convert* a whole C program to Ada, ...
    (comp.lang.ada)
  • Literate Programming in Ada, AdaDoc, AdaBrowse
    ... I've been struggling with the question of how best to do the documentation ... accompanying open source Ada projects. ... Literate programming is a fancy way of documenting source code. ... These ideas lead us to the existing AdaDoc and AdaBrowse projects, ...
    (comp.lang.ada)
  • Re: Literate Programming in Ada, AdaDoc, AdaBrowse
    ... > documentation accompanying open source Ada projects. ... for things that are too complex for Ada ... > (particularly the package specifications), ...
    (comp.lang.ada)
  • Re: Ada OS
    ... Location of the main documentation and links ... the "c2ada" the program should be used on itself. ... C code to a standard Ada 95 code. ... SourceForce that is hurting SourceForce as well as the OSI. ...
    (comp.lang.ada)
  • Re: Ada OS
    ... If a person manages an Ada project they should insure that each version ... But if more than two languages are use most people ... not insure that the c2ada project is full functional before he posted it. ... C code to a standardAda95 code. ...
    (comp.lang.ada)