 
| Subject: | |
| From: | |
| Reply To: | [log in to unmask][log in to unmask]> wrote: > A middle > ground may be found by including the beta as an unsupported patch > made available on JAZZ and include the results of those people opting > that route in the decision to GR a patch. let's talk about this idea.... i know this thought has been mentioned over and over. to 'us' it seems logical and simple and a good idea. [...]46_5Aug200413:42: [log in to unmask] |
| Date: | Mon, 2 Aug 2004 14:53:40 -0700 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Jeff Vance wrote about CI user functions:
> We are considering backporting this patch to earlier MPE
> releases, so if
> you have input for us on that topic please let me know -- I
It should be backported to any version that is in any way supported - in
this case, 7.0 and 6.5.
As I noted several months ago, making CI user functions available on all
"supported" releases of MPE/iX has a positive impact on the new CI "info"
function development. These can be developed as programs and accessed
through the CI using an appropriate wrapper command file or UDC. It would
make them easier to develop and deploy and could be deployed over all
"supported" systems at little or no incremental cost.
Someone suggested that the problem with my idea is the process creation
overhead, to which I respond that if you are calling a CI function 100s or
1000s of times in a loop, you should probably write a program that uses the
AIFs directly anyway if performance is a concern.
John Burke
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|
