TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To: Jeff Carter <[log in to unmask]>
Date: Sun, 3 Dec 2000 21:53:31 -0500
Reply-To: Jesse Farmer <[log in to unmask]>
From: Jesse Farmer <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Parts/Attachments: text/plain (26 lines)
Actually, although he didn't specifiy it, essentially, what Stephane
Richard was talking about was a sort of high speed database using global
arrays.
While I think you are quite right, that global variable are often not good,
this is a unique application, not really typical of arrays.
And arrays ARE the fastest form of managing lists of data in Ada right?  As
opposed to linked lists (which are faster in C)?
Stephane's application is one where you certainly wouldnt want to be
bothered interfacing to an Access or Oracle database, or a propritary database.

This is probably the best way to do this isn't it?  Via global arrays?

-Jesse Farmer

At 11:53 AM 12/3/00 -0600, you wrote:
>What you are talking about is a global variable. Global variables cause
>disease, famine, and war, not to mention really badly designed,
>impossible-to-debug software. The first rule of software engineering is
>modularize and never use global variables. The first two rules of
>software engineering ...
>
>--
>Jeff Carter
>"Nobody expects the Spanish Inquisition!"
>Monty Python's Flying Circus

ATOM RSS1 RSS2