Sponsored Content
Full Discussion: vswprintf missing in HP-UX
Top Forums Programming vswprintf missing in HP-UX Post 57458 by maestro@altiris on Thursday 28th of October 2004 10:23:32 AM
Old 10-28-2004
vswprintf missing in HP-UX

I am writing software that should be running on HP-UX versions 11.00 and 11i. There will be one set of binaries and I need to use the vswprintf() function. Unfortunately, it is not available on HP-UX 11.00. Neither are available other wprintf() family functions.

Is there any workaround for this problem? Are there any free implementations of these functions or is it anyhow possible to take the implementation from HP-UX 11i and distribute it along with our software so that it could also work on HP-UX 11.00?

Thanks in advance!
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

what am I missing?

I have the following portion of a script Check() { echo "\n\nChecking that all constraints are Enabled" echo "..." sleep 2 CHECK_COUNT='sqlplus -s $1 <<-EOSQL4 set feed off pause off pages 0 head off; set linesize 150 echo off; select count(*) from user_constraints where... (4 Replies)
Discussion started by: Zelp
4 Replies

2. Solaris

missing libsunmath.so.1

Hi, I have an application which requires libsunmath.so.1, however; my os version seems to be missing this file (find from root level did not return anything). Version: SunOS 5.10 where can I get this file? thanks, (1 Reply)
Discussion started by: orahi001
1 Replies

3. UNIX for Dummies Questions & Answers

missing scrollbar

Hi, My tcsh window doesn't have a scrollbar, so I don't get a lot of history! Can you help to get scrollbar? Thanks (3 Replies)
Discussion started by: parisa_3456
3 Replies

4. Linux

library missing

Hi, I am trying migrate webmin application from solaris to linux. But that is not working in Linux. because the library librpcsoc.so has missed in Linux box.. Could you please advice me that how to resolve this issue and also that how to install that library as well. (1 Reply)
Discussion started by: Mani_apr08
1 Replies

5. Shell Programming and Scripting

[: missing `]'

Hi, I am getting this error while running the following code. i=`awk '{print $2}' test1.txt` j=`awk '{print $4}' test1.txt` k=`awk '{print $6}' test1.txt` if ; then echo "Up." else echo "down" fi rm -f test.txt test1.txt error is this: line 12: ' Please suggest. (2 Replies)
Discussion started by: arijitsaha
2 Replies

6. Shell Programming and Scripting

Need help looking for missing hours.

I have a file that should cover a days worth of stats, at the beginning of each 15 minute report I have a unique header that looks like the below example. The "0000" and "0015" will change in the header line to show which 15 Minute interval the report is covering and of course from day to day the... (7 Replies)
Discussion started by: fsanchez
7 Replies

7. SuSE

How to resolve missing missing dependencies with opensuse 11.3 and 12.3?

Hello, This is a programming question as well as a suse question, so let me know if you think I should post this in programming. I have an application that I compiled under opensuse 12.2 using g77-3.3/g++3.3. The program compiles and runs just fine. I gave the application to a colleague who... (2 Replies)
Discussion started by: LMHmedchem
2 Replies

8. Red Hat

Yum - resolving missing dependencies that are not missing

I am trying to install VirtualBox on RHEL 5 but I need the 32 bit version for 32 bit Windows. When I run yum I get the following: sudo yum localinstall /auto/spvtg-it/spvss-migration/Software/VirtualBox-4.3-4.3.2_90405_el6-1.i686.rpm Loaded plugins: fastestmirror Setting up Local Package... (13 Replies)
Discussion started by: gw1500se
13 Replies

9. Programming

Missing cout

Heyas Me trying some C.. cout in specific, thats what i remembered: #include <stdio.h> // -- Just the above or with all the below ones, no change #include <stdio_ext.h> #include <stdlib.h> #include <wchar.h> //#include <iostream> // I assume its the same anyway? //#include <iostream.h>... (2 Replies)
Discussion started by: sea
2 Replies
WPRINTF(3)						     Linux Programmer's Manual							WPRINTF(3)

NAME
wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf - formatted wide character output conversion SYNOPSIS
#include <stdio.h> #include <wchar.h> int wprintf(const wchar_t *format, ...); int fwprintf(FILE *stream, const wchar_t *format, ...); int swprintf(wchar_t *wcs, size_t maxlen, const wchar_t *format, ...); #include <stdarg.h> int vwprintf(const wchar_t *format, va_list args); int vfwprintf(FILE *stream, const wchar_t *format, va_list args); int vswprintf(wchar_t *wcs, size_t maxlen, const wchar_t *format, va_list args); DESCRIPTION
The wprintf family of functions is the wide-character equivalent of the printf family of functions. It performs formatted output of wide characters. The wprintf and vwprintf functions perform wide character output to stdout. stdout must not be byte oriented; see function fwide for more information. The fwprintf and vfwprintf functions perform wide character output to stream. stream must not be byte oriented; see function fwide for more information. The swprintf and vswprintf functions perform wide character output to an array of wide characters. The programmer must ensure that there is room for at least maxlen wide characters at wcs. These functions are like the printf, vprintf, fprintf, vfprintf, sprintf, vsprintf functions except for the following differences: o The format string is a wide character string. o The output consists of wide characters, not bytes. o swprintf and vswprintf take a maxlen argument, sprintf and vsprintf do not. (snprintf and vsnprintf take a maxlen argument, but these functions do not return -1 upon buffer overflow on Linux.) The treatment of the conversion characters c and s is different: c If no l modifier is present, the int argument is converted to a wide character by a call to the btowc function, and the resulting wide character is written. If an l modifier is present, the wint_t (wide character) argument is written. s If no l modifier is present: The ``const char *'' argument is expected to be a pointer to an array of character type (pointer to a string) containing a multibyte character sequence beginning in the initial shift state. Characters from the array are converted to wide characters (each by a call to the mbrtowc function with a conversion state starting in the initial state before the first byte). The resulting wide characters are written up to (but not including) the terminating null wide character. If a precision is specified, no more wide characters than the number specified are written. Note that the precision determines the number of wide characters written, not the number of bytes or screen positions. The array must contain a terminating null byte, unless a precision is given and it is so small that the number of converted wide characters reaches it before the end of the array is reached. -- If an l modifier is present: The ``const wchar_t *'' argument is expected to be a pointer to an array of wide characters. Wide characters from the array are written up to (but not including) a terminating null wide character. If a precision is specified, no more than the number specified are written. The array must contain a terminating null wide character, unless a precision is given and it is smaller than or equal to the number of wide characters in the array. RETURN VALUE
The functions return the number of wide characters written, excluding the terminating null wide character in case of the functions swprintf and vswprintf. They return -1 when an error occurs. CONFORMING TO
ISO/ANSI C, UNIX98 SEE ALSO
printf(3), fprintf(3), snprintf(3), fputwc(3), fwide(3), wscanf(3) NOTES
The behaviour of wprintf et al. depends on the LC_CTYPE category of the current locale. If the format string contains non-ASCII wide characters, the program will only work correctly if the LC_CTYPE category of the current locale at run time is the same as the LC_CTYPE category of the current locale at compile time. This is because the wchar_t representation is platform and locale dependent. (The GNU libc represents wide characters using their Unicode (ISO-10646) code point, but other platforms don't do this. Also, the use of ISO C99 universal character names of the form unnnn does not solve this problem.) Therefore, in interna- tionalized programs, the format string should consist of ASCII wide characters only, or should be constructed at run time in an interna- tionalized way (e.g. using gettext or iconv, followed by mbstowcs). GNU
1999-11-20 WPRINTF(3)
All times are GMT -4. The time now is 07:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy