代码搜索结果

descriptor statements have the following shortcomings - input descriptors (USING DESCRIPTOR ) are not supported Reason: to fully support dynamic SQL the frontend/backend communication s

#include /* * Getopt vars shared between getopt and gnu_getopt */ /* For communication from `getopt' to the caller. When `getopt' finds an option that takes an argument, the argum

/* This header file is used by both the application and the monitor. It is the linkage used to establish a communication path between the monitor and the application. */ #include "monlib.h" #d

/* This header file is used by both the application and the monitor. It is the linkage used to establish a communication path between the monitor and the application. */ #include "monlib.h" #d

/* This header file is used by both the application and the monitor. It is the linkage used to establish a communication path between the monitor and the application. */ #include "monlib.h" #d

/* This header file is used by both the application and the monitor. It is the linkage used to establish a communication path between the monitor and the application. */ #define STD_CMD 0

/* This header file is used by both the application and the monitor. It is the linkage used to establish a communication path between the monitor and the application. */ #define STD_CMD 0

# Host: Intel 386 running DGUX, cloned from SVR4 XM_FILE= xm-i386v4.h # for network communication XM_CLIBS= -lsocket -lnsl NAT_FILE= nm-i386v4.h NATDEPFILES= corelow.o core-regset.o fork-child.o i38

# Host: Intel 386 running SVR4 XM_FILE= xm-i386v4.h # for network communication XM_CLIBS= -lsocket -lnsl NAT_FILE= nm-i386v4.h NATDEPFILES= corelow.o core-regset.o fork-child.o i386v4-nat.o \ solib

# Host: Intel 386 running SVR4 XM_FILE= xm-i386v4.h # for network communication XM_CLIBS= -lsocket -lnsl # we don't want nm-i386v4.h since that defines LOSING_POLL which isn't # appropriate for i386