[Info-vax] AXIS2/C, gSOAP

[Jan-Erik Soderholm]

On 2010-08-29 15:47, Neil Rieck wrote:
> On Aug 27, 7:10 am, Jan-Erik Soderholm<jan-erik.soderh... at telia.com>
> wrote:
>> On 2010-08-27 01:53, Neil Rieck wrote:
>>
>>
>>
>>> On Aug 20, 3:32 pm, "John Reagan"<johnrrea... at earthlink.net>    wrote:
>>>> "Neil Rieck"<n.ri... at sympatico.ca>    wrote in message
>>
>>>> news:4b348bad-6985-4397-af41-
>>>> I am currently using BASIC 1.6 (for Alpha) and this switch is not
>>>> available. I can see in HP's most recent road map that they have
>>>> already released BASIC 1.7 and are working on BASIC 1.8. Can anyone
>>>> tell me if the "/name" switch is available in 1.8 or might be
>>>> available in 1.8 ?
>>
>>>> I don't remember seeing /NAME for BASIC on any of roadmaps (but then again,
>>>> I don't look much anymore).  Such features this are usually added based on
>>>> customer requests instead of just adding it to every compiler 'just for
>>>> fun'.    Also some languages like BLISS and Pascal have language syntax for
>>>> alternative spellings for externals (and allow mixed cased strings) so no
>>>> DCL qualifier is/was needed.
>>
>>>> I suggest you send in your request.
>>
>>>> John
>>
>>> That's too bad because something like this would allow BASIC programs
>>> to more easily link to other object files.
>>
>>> But to be honest, I remember the huge amount of re-engineering that
>>> went into making Visual BASIC 6 become Visual BASIC .NET so that VB
>>> could generate code similar to other MS languages. The changes caused
>>> a small revolt amongst the VB user community.  I guess I was hoping
>>> that HP would revamp VMS BASIC in a different way (like making
>>> variables case sensitive with the "/names" compiler switch seen
>>> elsewhere.
>>
>>> I still have my fingers crossed but am not holding my breath :-)
>>
>>> Neil Rieck
>>> Kitchener / Waterloo / Cambridge,
>>> Ontario, Canada.
>>> http://www3.sympatico.ca/n.rieck/OpenVMS.html
>>
>> This "/names" issue/questions got me thinking...
>>
>> COBOL doesn't have any switch for case-sensitivines either.
>> I do not use any "special" switch when compiling COBOL code
>> for use by gSOAP. Any COBOL/C/gSOAP incompatibility is taken
>> care of in the wrapper C-routine.
>>
>> Is BASIC different in any way in this regard then COBOL ?
>
> Which version of COBOL are you using? Unless it is a typo, the USER
> MANUAL for COBOL 2.8 does mention a compile switch called "/name"
>
> http://h71000.www7.hp.com/doc/82final/6297/aa-q2g1h-tk.pdf
>
> I'm not sure why it is not used in the gSOAP script for building a
> COBOL sample app. Maybe there a compatibility issue when linking to
> one of the other modules. (better run a note past Brett Cameron or
> John Apps)
>
> But to answer your question, BASIC would require a wrapper routine in
> order to link to a "C" program and the main reason is due to the CASE
> of the labels. (provided you don't have any other issues like
> differences in string structures, etc.). If you inspect the FORTRAN
> code in the gSOAP samples directory, you will notice that the build
> script does not use a wrapper.
>
> NSR

$ cobol /ver
HP COBOL V2.9-1453 on OpenVMS Alpha V8.3
$

Found it. Don't know what I did last time.
It's in "$ HELP COBOL QUA". Must have scrolled
passed that switch...

Anyway, I don't use it to compile COB files called from
the gSOAP/C-wrappers. COBOL also need the wrappers to
take care of null-terminated (in C/gSOAP) vs. fixed-lenght
strings (in COBOL).