<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Strdup, strcasecmp, and strncasecmp in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943775#M33072</link>
    <description>&amp;gt; [...] there are typedef declaration using&lt;BR /&gt;&amp;gt; this function [...]&lt;BR /&gt;&lt;BR /&gt;Eh?&lt;BR /&gt;&lt;BR /&gt;If you use the __CRTL_VER conditionality, you&lt;BR /&gt;could avoid your original problem, namely, a&lt;BR /&gt;mismatch between the system header file and&lt;BR /&gt;your function declaration, and you would not&lt;BR /&gt;need to change your function.&lt;BR /&gt;&lt;BR /&gt;One way, you add a couple of directives to a&lt;BR /&gt;couple of files.  The other way, you change&lt;BR /&gt;the same files plus the compile command. It's&lt;BR /&gt;your decision.  There's almost always more&lt;BR /&gt;than one way to solve a problem (but my way&lt;BR /&gt;is usually better).&lt;BR /&gt;&lt;BR /&gt;This exact method is used in the Info-ZIP&lt;BR /&gt;Zip program version 2.31 (and higher), and&lt;BR /&gt;(so far as I know) it gets built happily&lt;BR /&gt;from VMS V5.4 through V8.2, VAX C and DEC C&lt;BR /&gt;(specifying /PREFIX = ALL), on VAX, Alpha,&lt;BR /&gt;and IA64, at least. (Plus an old GNU C on&lt;BR /&gt;the VAX.)  It seems to work pretty well.</description>
    <pubDate>Thu, 01 Dec 2005 01:29:26 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2005-12-01T01:29:26Z</dc:date>
    <item>
      <title>Strdup, strcasecmp, and strncasecmp</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943774#M33071</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;I purposly added this /PREFIX=EXCEPT=AnyDuplicateCRTLFunction to avoid cimpilation errors and link time errors.&lt;BR /&gt;&lt;BR /&gt;===================&lt;BR /&gt;list/mach/noopt/debug/define=("vms")/prefix=except=strnncasecmp/nomember/assume=noaligned_obj.&lt;BR /&gt;===================&lt;BR /&gt;&lt;BR /&gt;I accept your idea of modifying only in two places. But as I said, this functions are being used in most of the programs, there are typedef declaration using this function, function return variables, etc...&lt;BR /&gt;&lt;BR /&gt;Important thing here is that, we don't want to comment out this function declarations and definitions as we want to keep this 15 years old programs compatible for both VAX/VMS and Alpha/OpenVMS developement. __DECC, __CRTL_VER, and __VMS_VER conditions were already added for this purpose.&lt;BR /&gt;&lt;BR /&gt;Except these new directives check, I don't have plan of touching the codes at this moment. Probably I may go with your suggestions once we get fresh requirements in the IInd qtr of 2006.&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
      <pubDate>Thu, 01 Dec 2005 00:43:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943774#M33071</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2005-12-01T00:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: Strdup, strcasecmp, and strncasecmp</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943775#M33072</link>
      <description>&amp;gt; [...] there are typedef declaration using&lt;BR /&gt;&amp;gt; this function [...]&lt;BR /&gt;&lt;BR /&gt;Eh?&lt;BR /&gt;&lt;BR /&gt;If you use the __CRTL_VER conditionality, you&lt;BR /&gt;could avoid your original problem, namely, a&lt;BR /&gt;mismatch between the system header file and&lt;BR /&gt;your function declaration, and you would not&lt;BR /&gt;need to change your function.&lt;BR /&gt;&lt;BR /&gt;One way, you add a couple of directives to a&lt;BR /&gt;couple of files.  The other way, you change&lt;BR /&gt;the same files plus the compile command. It's&lt;BR /&gt;your decision.  There's almost always more&lt;BR /&gt;than one way to solve a problem (but my way&lt;BR /&gt;is usually better).&lt;BR /&gt;&lt;BR /&gt;This exact method is used in the Info-ZIP&lt;BR /&gt;Zip program version 2.31 (and higher), and&lt;BR /&gt;(so far as I know) it gets built happily&lt;BR /&gt;from VMS V5.4 through V8.2, VAX C and DEC C&lt;BR /&gt;(specifying /PREFIX = ALL), on VAX, Alpha,&lt;BR /&gt;and IA64, at least. (Plus an old GNU C on&lt;BR /&gt;the VAX.)  It seems to work pretty well.</description>
      <pubDate>Thu, 01 Dec 2005 01:29:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943775#M33072</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2005-12-01T01:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Strdup, strcasecmp, and strncasecmp</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943776#M33073</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;Yes, we did not use __CRTL_VER check initially, for that we used /PREFIX=EXCEPT=xxx to bypass the compilation and linking warnings. It worked.&lt;BR /&gt;&lt;BR /&gt;Thanks for Steven for your suggestions. I will come back to you if I have any more problems on this now and later when we may go for big enancement work probably in 2006.&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
      <pubDate>Thu, 01 Dec 2005 11:08:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strdup-strcasecmp-and-strncasecmp/m-p/4943776#M33073</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2005-12-01T11:08:38Z</dc:date>
    </item>
  </channel>
</rss>

