VEC_$IABS16                       Domain/OS                        VEC_$IABS16


NAME
     vec_$iabs16 - take the absolute value of the elements in a 16-bit integer
     vector

SYNOPSIS (C)
     #include <apollo/base.h>
     #include <apollo/vec.h>

     void vec_$iabs16(
          short int *start_vec,
          long int &length,
          short int *result_vec)

SYNOPSIS (Pascal)
     %include '/sys/ins/base.ins.pas';
     %include '/sys/ins/vec.ins.pas';

     procedure vec_$iabs16(
          in start_vec: univ vec_$integer16_vector;
          in length: integer32;
          out result_vec: univ vec_$integer16_vector);

SYNOPSIS (FORTRAN)
     %include '/sys/ins/base.ins.ftn'
     %include '/sys/ins/vec.ins.ftn'

           parameter (nvec = 10)

           integer*2 start_vec(nvec), result_vec(nvec)
           integer*4 length

           call vec_$iabs16(start_vec, length, result_vec)

DESCRIPTION
     Vec_$iabs16 places the absolute value of the entries in the vector
     start_vec into result_vec.  The calculation performed is as follows:

     For each integer I such that 1 <= I <= length,

     result_vec(I) = |start_vec(I)|
                     |            |
     start_vec
          The vector whose absolute value is required.

     length
          The number of elements to be operated on;  normally the same as the
          number of elements in the vectors.

     result_vec
          The absolute value of the vector start_vec.

NOTES
     When vec_$iabs16 is used to operate on matrixes in C and Pascal,
     start_vec and result_vec are row vectors; in FORTRAN, they are column
     vectors.

     As in all the vec_$ calls,  the result array must not overlap any of the
     input arrays; the result array may be identical to an input, but must not
     contain any subset of it.   Because of pipelining, using overlapping
     input and output arrays may cause incorrect results.

     Vec_$iabs16, like all 16-bit integer routines, performs poorly when
     compared to the 32-bit integer routines.  Its use should be avoided wher-
     ever possible, especially on high-performance workstations.

SEE ALSO
     vec_$neg, vec_$abs_i, vec_$dabs, vec_$dabs_i, vec_$abs, vec_$iabs_i,
     vec_$iabs16, vec_$iabs16_i.