>>>>    First the update:
 
After post-IPROF discussion with HP, it is now my
understanding that the "shareware" FSF GNU  C++
compiler that HP talked about bringing to the 3000 at
IPROF *will* be supported by HP;  i.e.:  The compiler
itself will be downloadable from JAZZ or whatever,
but users will have the option to purchase software
support for that compiler directly from HP (I assume
what this means is that HP will contract with the third
party to act as the lab for C++).  This sounds like at
least one big step in the right direction to me.
 
Something else I wasn't aware of (maybe old news
to many of you, but new to me):   Most other vendors
who have C++ compilers on their platforms apparently
use the shareware C++ product as a base for what
they provide.  If that is the case, having a 3000 version
of GNU  C++ should mean it will be easier to port C++
programs from other vendor platforms, compared to
porting C++ from HP-UX.  And a 3000 GNU C++ can
be available much faster than a port from UX....  Since
we need C++ on the 3000 ASAP for the client-server
extension to our Transact system that we are working
on, this is a major factor for our site....
 
HP is saying they want to work with the user community
to come up with the best doable solution for C++ on
MPE.  In an effort to provide additional detailed feedback
to HP, I have more-or-less volunteered to solict further
comment from 3000-L .......  Yes, I know;  another survey.
But at least this isn't one of those "give me a business
justification" things.......  And for those of you who are or
are contemplating evolving part of your system to client-
server or etc., IMHO it is worth filling out another survey
if that can help get C++ done right on the 3000.
 
>>>>    Now the feedback request:
 
For those of you who have opinions regarding  C++ on
MPE, please return completed surveys directly to me.
I will post summary to the list and forward to HP.
 
**** SURVEY FOLLOWS ****
 
thanks,
Ken Sletten
[log in to unmask]
360-396-2525
======================================
 
***   C++ on MPE/iX:   Requirements and Options   ***
 
1)   If a compiler existed which handled only Unix-like
constructs (at least initially) were supported, would
you use it ?
 
2)   If an MPE C++ compiler were enhanced after the
initial port, what capabilities would it need:  indicate
"don't care", "useful", or "must have" for each ?
        Intrinsic support:
        Access to IMAGE:
        Access to KSAM:
        Long pointer support:
        Ability to run in MPE Name Space:
        Use default MPE naming conventions:
        Other >________________________:
 
3)   Would you trust a third-party compiler that was
supported by HP ?
 
4)   What would you be willing to pay HP for annual
support of C++ on MPE/iX ?
 
5)   If the cost of acquisition of the compiler were
minimal or non-existent, would you be willing to pay
higher support fees over a guaranteed term ?
 
6)   Additional comments/remarks/concerns on this
subject:
 
======================================
Please email completed surveys directly to:
              [log in to unmask]
======================================