[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Which programming Language



On Sun, Feb 08, 2009 at 12:56:48AM -0500, Michael Pobega wrote:
> On Sat, Feb 07, 2009 at 08:20:30PM -0500, Douglas A. Tutty wrote:
> > On Sat, Feb 07, 2009 at 11:40:29AM -0500, Michael Pobega wrote:
> > > On Sat, Feb 07, 2009 at 09:39:20AM -0500, Douglas A. Tutty wrote:
> > > > On Fri, Feb 06, 2009 at 06:25:31PM +0100, Abdelkader Belahcene wrote:
 
> > This is why I'm transitioning to Ada.  If I have to port anyway, I may
> > as well port to a compiled language.  Ada was written as a standard long
> > before the first compiler was done, then the compilers had to meet the
> > standard.  Ada programs are totally portable from one machine to another
> > (unless, of course, you import a non-Ada function that is not the same
> > on all machines).  Ada is designed to allow for the long-term
> > maintenance of programs.  
 
> 
> As true as this is, are there any good libraries written for Ada?

Gnat itself uses a source-based library system.  There are plenty of
specialized libraries available on the web-sites I suggested (and lots
arround elsewhere).  Since there in source form, you can easily audit
them before use.  Debian has several specialized ones (e.g. to use GTK+
to make GUIs) in the repository.

If none of them help, or you need to access libc, just access it
directly:

8>-
function gettime return long_integer;
pragma import( C, gettime);
8>-

Now you can use gettime as if it were an Ada library.  Since its in the
standard C library, you don't have to specify a special library when you
run gnatmake.

> also, you can just compile your Python code and you won't run into that
> problem.

Someone has a python compiler (*.py to an executable)?  Yes, I know that
python *.py modules get "compiled" into *.pyc byte-code but that still
has to go through the python interpreter.  Also, what happens in 10
years when I want to make a slight change to a program?

Doug.


Reply to: