menu_new(3MENU)menu_new(3MENU)NAME
mitem_new - create and destroy menu items
SYNOPSIS
#include <menu.h>
ITEM *new_item(const char *name, const char *description);
int free_item(ITEM *item);
DESCRIPTION
The function new_item allocates a new item and initializes it from the name and description pointers. Please notice that the item stores
only the pointers to the name and description. Those pointers must be valid during the lifetime of the item. So you should be very careful
with names or descriptions allocated on the stack of some routines.
The function free_item de-allocates an item. Please notice that it is the responsibility of the application to release the memory for the
name or the description of the item.
RETURN VALUE
The function new_item returns NULL on error. It sets errno according to the function's failure:
E_BAD_ARGUMENT
Routine detected an incorrect or out-of-range argument.
E_SYSTEM_ERROR
System error occurred, e.g., malloc failure.
The function free_item returns one of the following:
E_OK The routine succeeded.
E_BAD_ARGUMENT
Routine detected an incorrect or out-of-range argument.
E_CONNECTED
Item is connected to a menu.
E_SYSTEM_ERROR
System error occurred (see errno).
SEE ALSO ncurses(3NCURSES), menu(3MENU).
NOTES
The header file <menu.h> automatically includes the header file <curses.h>.
PORTABILITY
These routines emulate the System V menu library. They were not supported on Version 7 or BSD versions.
AUTHORS
Juergen Pfeifer. Manual pages and adaptation for new curses by Eric S. Raymond.
menu_new(3MENU)
Check Out this Related Man Page
menu_new(3MENU)menu_new(3MENU)NAME
menu_new - create and destroy menu items
SYNOPSIS
#include <menu.h>
ITEM *new_item(const char *name, const char *description);
int free_item(ITEM *item);
DESCRIPTION
The function new_item allocates a new item and initializes it from the name and description pointers. Please notice that the item stores
only the pointers to the name and description. Those pointers must be valid during the lifetime of the item. So you should be very careful
with names or descriptions allocated on the stack of some routines.
The function free_item de-allocates an item. Please notice that it is the responsibility of the application to release the memory for the
name or the description of the item.
RETURN VALUE
The function new_item returns NULL on error. It sets errno according to the function's failure:
E_BAD_ARGUMENT
Routine detected an incorrect or out-of-range argument.
E_SYSTEM_ERROR
System error occurred, e.g., malloc failure.
The function free_item returns one of the following:
E_OK The routine succeeded.
E_BAD_ARGUMENT
Routine detected an incorrect or out-of-range argument.
E_CONNECTED
Item is connected to a menu.
E_SYSTEM_ERROR
System error occurred (see errno).
SEE ALSO ncurses(3NCURSES), menu(3MENU).
NOTES
The header file <menu.h> automatically includes the header file <curses.h>.
PORTABILITY
These routines emulate the System V menu library. They were not supported on Version 7 or BSD versions.
AUTHORS
Juergen Pfeifer. Manual pages and adaptation for new curses by Eric S. Raymond.
menu_new(3MENU)
So, I've been told and heard a million times that malloc and free are expensive calls to be avoided. So many times I avoid malloc by reusing already allocated memory blocks. Store them on free lists somewhere myself and don't call free when I know malloc will be called very shortly thereafter.
... (6 Replies)
I have a field MPN-BANK-NUMBERO:006,00:N in a file FILE1
How can i display the length of the Bank Number.Any idea ?
The output shud take the following format
FILE 1 6
Where 1 is the starting position and 6 is the Ending position. (9 Replies)
We have an old ProLiant ML370 server (10-15 years old) running SCO (version yet to be confirmed), with a single bespoke Cobol app. The server is failing and I need to get the app up and running on new hardware or cloud.
I've supported ProLiant servers running Windows for many years but have... (12 Replies)