Sponsored Content
Full Discussion: Function Returning Pointer
Top Forums Programming Function Returning Pointer Post 302506800 by majid.merkava on Tuesday 22nd of March 2011 02:40:37 AM
Old 03-22-2011
Function Returning Pointer

Hi guys.

how a functions such fdopen, ... can return pointer?
are these functions use static memory(variables)?
 

10 More Discussions You Might Find Interesting

1. Programming

Problem with function which reutrns pointer to a value

i have a function: char *pcCityIdToCountryName(ADMIN_DB_DATA *pstHEader, unit uiCityID) this returns a pointer to CountryName if cityId is given. to retrieve countryname i give: char *CountryName; CountryName = pcCityIdToCountryName(..................); but when i compile it is giving :... (5 Replies)
Discussion started by: jazz
5 Replies

2. Programming

string returning function

I have two string returning function in ESQL/C char *segment_name(lbuffer) char *lbuffer; {..... and char *get_bpdvalue(f_name) char *f_name; {...... both declared above main() char *get_bpdvalue(); char *segment_name(); my problem is segment_name works on sprintf and strcpy... (5 Replies)
Discussion started by: jisc
5 Replies

3. Programming

How to return void function pointer

Hello all im trying to build function that will return void function pointer what is mean is ( not working ) the main function void * myClass::getFunction(int type){ if(type==1) return &myClass::Test1; if(type==2) return &myClass::Test2; } void myClass::Test1(){... (1 Reply)
Discussion started by: umen
1 Replies

4. Shell Programming and Scripting

returning from a function

Hi all, I am very new to BASH shell programming. I need to return an integer from a function to the caller function. I did this: but it keeps giving me wrong return: Can someone help me out here, please? Thanks (2 Replies)
Discussion started by: alirezan
2 Replies

5. Shell Programming and Scripting

Returning the name of function used

Hi All In my script, I can call on several functions. I have a logging function that is called by any of these functions. What I would like is some way of identifying which function I am using and pass this to the log function as some parameter. Is there some built in command or way of... (3 Replies)
Discussion started by: kingpin2502
3 Replies

6. Programming

Function pointer to inline function ?

Hi. Problem: I have to parse the payload of a packet. The payload could be in Big Endian Format (network byte order) or little. That depends on a flag present in the header of the packet. Solution: A horrible solution could be to check for that flag everytime I have to read a field in the... (11 Replies)
Discussion started by: emitrax
11 Replies

7. Programming

structure pointer array as function parameters

if i create an array of pointers to a structure "struct node" as: struct node *r; and create "n" number of "linked lists" and assign it to the various struct pointers r using some function with a return type as structure pointer as: r=multiplty(.......) /*some parameters*/ is... (2 Replies)
Discussion started by: mscoder
2 Replies

8. Programming

Trivial doubt about C function pointer

Hi, In the below C code, #include <stdio.h> void print() { printf("Hello\n"); } int main() { void (*f)() = (void (*)()) print; f(); (*f)(); } I wonder, how the syntaxes "f()" and "(*f)()" are treated as same without any error? Is this an improvement or ANSI/ISO... (1 Reply)
Discussion started by: royalibrahim
1 Replies

9. Programming

Pure C function pointer on printing vowels twice

Have difficulty to understand this pure C code to only print vowels twice from input string. Questions are commented at the end of each place. #include <stdio.h> #include <stdlib.h> #include <assert.h> #include <limits.h> /* *Demonstrate the use of dispatch tables */ /*Print a char... (11 Replies)
Discussion started by: yifangt
11 Replies

10. Programming

Segmentation fault when I pass a char pointer to a function in C.

I am passing a char* to the function "reverse" and when I execute it with gdb I get: Program received signal SIGSEGV, Segmentation fault. 0x000000000040083b in reverse (s=0x400b2b "hello") at pointersExample.c:72 72 *q = *p; Attached is the source code. I do not understand why... (9 Replies)
Discussion started by: jose_spain
9 Replies
explain_fdopen(3)					     Library Functions Manual						 explain_fdopen(3)

NAME
explain_fdopen - explain fdopen(3) errors SYNOPSIS
#include <libexplain/fdopen.h> const char *explain_fdopen(int fildes, const char *flags); const char *explain_errno_fdopen(int errnum, int fildes, const char *flags); void explain_message_fdopen(char *message, int message_size, int fildes, const char *flags); void explain_message_errno_fdopen(char *message, int message_size, int errnum, int fildes, const char *flags); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the fdopen(3) system call. explain_fdopen const char *explain_fdopen(int fildes, const char *flags); The explain_fdopen function is used to obtain an explanation of an error returned by the fdopen(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: FILE *fp = fdopen(fildes, flags); if (!fp) { fprintf(stderr, "%s ", explain_fdopen(fildes, flags)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_fdopen_or_die(3) function. fildes The original fildes, exactly as passed to the fdopen(3) system call. flags The original flags, exactly as passed to the fdopen(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_fdopen const char *explain_errno_fdopen(int errnum, int fildes, const char *flags); The explain_errno_fdopen function is used to obtain an explanation of an error returned by the fdopen(3) system call. The least the mes- sage will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: FILE *fp = fdopen(fildes, flags); if (!fp) { int err = errno; fprintf(stderr, "%s ", explain_errno_fdopen(err, fildes, flags)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_fdopen_or_die(3) function. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fdopen(3) system call. flags The original flags, exactly as passed to the fdopen(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_fdopen void explain_message_fdopen(char *message, int message_size, int fildes, const char *flags); The explain_message_fdopen function may be used to obtain an explanation of an error returned by the fdopen(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: FILE *fp = fdopen(fildes, flags); if (!fp) { char message[3000]; explain_message_fdopen(message, sizeof(message), fildes, flags); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_fdopen_or_die(3) function. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. fildes The original fildes, exactly as passed to the fdopen(3) system call. flags The original flags, exactly as passed to the fdopen(3) system call. explain_message_errno_fdopen void explain_message_errno_fdopen(char *message, int message_size, int errnum, int fildes, const char *flags); The explain_message_errno_fdopen function may be used to obtain an explanation of an error returned by the fdopen(3) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: FILE *fp = fdopen(fildes, flags); if (!fp) { int err = errno; char message[3000]; explain_message_errno_fdopen(message, sizeof(message), err, fildes, flags); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_fdopen_or_die(3) function. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fdopen(3) system call. flags The original flags, exactly as passed to the fdopen(3) system call. SEE ALSO
fdopen(3) stream open functions explain_fdopen_or_die(3) stream open functions and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_fdopen(3)
All times are GMT -4. The time now is 10:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy