Re: How does this software work?? -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

----- Original Message -----
From: "Hall, Philip" <phall@spss.com>
>
> There are TAATOOLS (when they were still free in QUSRTOOL) that broke at
> different release levels, unless you recompiled the new source for them
that
> came with that new release. Although, granted, they never used really
> 'undocumented' stuff.

Before there were all the system api's, I can see the tool code breaking,
but what v5r1 tool would be release dependent and why?



> > The system needs PKCS #1 thru 15 as open source api's,
> > written in MI for best performance and compatibility.
>
> Why do you think MI will give you 'best performance and compatibility' ?
> Why not just hand-code the PCC assembly language ?

You are forgetting "and compatibility". MI helps prove my point. You can
code low level and still be release and hardware independent.

I dont think we have any choice.  If your utility or api does not work after
an upgrade, than it is probably more trouble than it is worth.  Requiring a
recompile may be ok, but even that has the potential for customer downtime
or worse.

-Steve

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.