| Title: | Languages |
| Notice: | Speaking In Tongues |
| Moderator: | TLE::TOKLAS::FELDMAN |
| Created: | Sat Jan 25 1986 |
| Last Modified: | Wed May 21 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 394 |
| Total number of notes: | 2683 |
I'm passing along a few questions for somebody who doesn't have
access to notes.
1. Is there a document that specifies the run-time performance
of the various VAX languages?? The customer had such a beast
about 6 years ago ... is there a current document?
2. The same customer was told by a software specialist who is
no longer around, that DEC had a document that addresses
when to use modular code vs non-modular code. Anything known
that address modular code at all would be helpful.
Donna who_is_just_playing_messenger
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 231.1 | same; always | SAUTER::SAUTER | John Sauter | Tue Apr 18 1989 07:09 | 11 |
I believe the "party line" is that all of the compiled languages have
roughly the same performance. You should choose a language based how
well its syntax and semantics match the problem you are solving, not on
its performance.
In my opinion, you should always write modular code. You never know
when somebody might be able to use your code as part of a larger
solution. There are details about "modular programming" in the VMS
doc set: ``Guide to Creating Modular Procedures'', Programming volume
1.
John Sauter
| |||||
| 231.2 | There Was One | BMT::BOWERS | Count Zero Interrupt | Tue Apr 18 1989 09:13 | 3 |
There was such a discussion in the old "VAX Technical Summary" which,
in particular, touted the excellent performance of VAX BASIC for
computational applications ( a prime nmuber sieve was the example).
| |||||