Wayne R. Boyer wrote:
> In a message dated 6/26/02 5:58:09 PM Pacific Daylight Time,
> [log in to unmask] writes:
>
>
>> You could put your lookup/decision routine into a subroutine in an
>> XL.  If you set it up right you can change a hardwired constant by
>> rebuilding the XL, without recompiling or re-linking the
>> applications.  Probably even change the XL to do a data-base lookup
>> instead of having a hardwired constants without recompiling
>> applications, as long as you don't change the subroutine parms.
>>
>>
>
> This is an EXCELLENT approach.  I've written some routines that work
> like this and I've been very happy with the results.  I originally
> found this idea within MANMAN.  MANMAN has a large library of
> subroutines and some of them do this kind of thing.  Someday I'll get
> to write a lot of new code that works this way.

Sorry to disagree with you, Wayne, but for me this blows chunks, big time.

You might as well keep your code in an Image database (though no doubt someone
will pop up who *does* - probably Wirt :-) ).

Whose data is it? Who are applications for? It might - just - be acceptable to
keep application control parameters (metadata) that no user should ever touch
in such a place, but if it's real data, it should be out where the users can
change it if they need to.

And I take it that MANMAN comes with a free Fortran compiler, and a user
training manual, so that the developers, even, can look after this stuff?

And don't even get me started on version control, testing, regression testing,
multi-country roll-outs, on-the-fly installation, and all the other 'good'
things that come with changing the code of an application - as that is what
you are doing - if you do it properly.

Also, is this a *portable* approach, or is it based on quirks of the HP3000?
'Oh, yeah, we ported your app to Windows, and we just made all the XLs into
.DLLs, no sweat. Can you please just sign here for this .net development kit?
You'll need it if you ever want to change the base price of fuel oil.'

DATA<> CODE!

Then again, I wouldn't even consider keeping *any* base data, (assuming it is
to be used within an Image app) no matter how 'static', outside my database. I
just can't think of a single good reason to do so, not one. Security, access,
backup, recovery, data handling, moving the application - is there *anything*
a flat file can offer that is superior to an Image file?




--
Roy Brown

Posting with the OEnemy, tamed by OE-QuoteFix
http://jump.to/oe-quotefix

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *