Package “ClearSilver” has 120 man pages.
cBroadcast(3) Broadcasts a signal to all threads waiting on condition variable <cond>. MT-Level: Safe. cCreate(3) Initializes the condition variable <cond>. MT-Level: Safe for unique <cond>. cDestroy(3) Destroys the condition variable <cond> that was initialized by cCreate(). MT-Level: Safe for unique <cond>. cgi_cookie_authority(3) cgi_cookie_authority will walk the CookieAuthority portion of the CGI HDF data set, and return the matching domain if it exists. The purpose of this is so that... cgi_cookie_clear(3) cgi_cookie_clear will send back a Set-Cookie string that will attempt to stop a browser from continuing to send back a cookie. Note that the cookie has to match... cgi_cookie_set(3) cgi_cookie_set will issue a Set-Cookie header that should cause a browser to return a cookie when required. Note this function does no escaping of anything, you... cgi_cs_init(3) cgi_cs_init initializes a CS parser with the CGI HDF context, and registers the standard CGI filters cgi_debug_init(3) cgi_debug_init initializes a CGI program for standalone debugging. By running a ClearSilver CGI program with a filename on the command line as the first... cgi_destroy(3) cgi_destroy will destroy all the data associated with a CGI, which mostly means the associated HDF and removal of any files that were uploaded via... cgi_display(3) cgi_display will render the CS template pointed to by cs_file using the CGI's HDF data set, and send the output to the user. Note that the output is actually... cgi_error(3) cgi_error will output a 500 error containing the specified error message. This function is likely to be removed from future versions in favor of a user error... cgi_filehandle(3) cgi_filehandle will return the stdio FILE pointer associated with a file that was uploaded using multipart/form-data. The FILE pointer is positioned at the... cgi_init(3) cgi_init initializes the ClearSilver CGI environment, including creating the HDF data set. It will then import the standard CGI environment variables into that... cgi_neo_error(3) cgi_neo_error will output a 500 error containing the NEOERR call backtrace. This function is likely to be removed from future versions in favor of some sort of... cgi_output(3) Normally, this is called by cgi_display, but some people wanted it external so they could call it directly. cgi_parse(3) We split cgi_init into two sections, one that parses just the basics, and the second is cgi_parse. cgi_parse is responsible for parsing the entity body of the... cgi_redirect(3) cgi_redirect will redirect the user to another page on your site. This version takes only the path portion of the URL. As with all printf style commands, you... cgi_redirect_uri(3) cgi_redirect_uri will redirect the user to another page on your site. This version takes the full URL, including protocol/domain/port/path. As with all printf... cgi_register_parse_cb(3) The ClearSilver CGI Kit has built-in functionality to handle the following methods: GET -> doesn't have any data except query string, which is processed for all... cgi_url_escape(3) cgi_url_escape will do URL escaping on the passed in string, and return a newly allocated string that is escaped. Characters which are escaped include control... cgi_url_escape_more(3) cgi_url_escape_more will do URL escaping on the passed in string, and return a newly allocated string that is escaped. Characters which are escaped include... cgi_url_unescape(3) cgi_url_unescape will do URL unescaping on the passed in string. This function modifies the string in place This function will decode any %XX character, and... cgi_url_validate(3) cgi_url_validate will check that a URL starts with one of the accepted safe schemes. If not, it returns "#" as a safe substitute. Currently accepted schemes are... cgi_vredirect(3) cgi_vredirect is mostly used internally, but can be used if you need a varargs version of the function. cgiwrap_getenv(3) cgiwrap_getenv wraps the getenv function for access to environment variables, which are used to pass data to CGI scripts. This version differs from the system... cgiwrap_init_emu(3) cgiwrap_init_emu sets up the cgiwrap subsystem for use in an emulated environment where you are providing routines to use in place of the standard routines, ie... cgiwrap_init_std(3) cgiwrap_init_std will initialize the cgiwrap subsystem to use the default CGI functions, ie getenv/putenv/stdio. In reality, all this is doing is setting up the... cgiwrap_iterenv(3) cgiwrap_iterenv allows a program to iterate over all the environment variables. This is probably mostly used by the default debug output. cgiwrap_putenv(3) cgiwrap_putenv wraps the putenv call. This is mostly used by the cgi_debug_init function to create an artificial environment. This version differs from the... cgiwrap_read(3) cgiwrap_read is used to read incoming data from the client, usually from a POST or PUT HTTP request. It wraps the part of fread(stdin). cgiwrap_write(3) cgiwrap_write is the block data output function for cgiwrap that replaces fwrite(stdout) in regular CGIs cgiwrap_writef(3) cgiwrap_writef is the formatted output command that replaces printf or fprintf(stdout) in a standard CGI cgiwrap_writevf(3) cgiwrap_writevf is the formatted output command that replaces vprintf or fvprintf(stdout) in a standard CGI It is also used by cgiwrap_writef (the actual... cs_destroy(3) cs_destroy will clean up all the memory associated with a CSPARSE structure, including strings passed to cs_parse_string. This does not clean up any memory... cs_dump(3) cs_dump will dump the CS parse tree in the parse struct. This can be useful for debugging your templates. This function also uses the CSOUTFUNC callback to... cSignal(3) Sends a signal to one thread waiting on condition variable <cond>. MT-Level: Safe. cs_init(3) cs_init will create a CSPARSE structure and initialize it. This structure maintains the state and information necessary for parsing and rendering a CS template... cs_parse_file(3) cs_parse_file will parse the CS template located at path. It will use hdf_search_path() if path does not begin with a '/'. The parsed CS template will be... cs_parse_string(3) cs_parse_string parses a string. The string is modified, and internal references are kept by the parse tree. For this reason, ownership of the string is... cs_register_esc_strfunc(3) cs_register_esc_strfunc functions exactly as cs_register_strfunc except that it changes the evaluation escaping context to disable default escaping. cs_register_fileload(3) cs_register_fileload registers a fileload function that overrides the built-in function. The built-in function uses hdf_search_path and ne_file_load (based on... cs_register_strfunc(3) cs_register_strfunc will register a string function that can be called during CS render. This not-callback is designed to allow for string formating/escaping... cs_render(3) cs_render will evaluate a CS parse tree, calling the CSOUTFUNC passed to it for output. Note that calling cs_render multiple times on the same parse tree may or... cWait(3) Waits for a signal on condition variable <cond>. The mutex <mutex> must be locked by the thread. MT-Level: Safe. dictCleanup(3) Calls <cleanup> for every item in <dict>. If <cleanup> returns true, then item is removed from <dict>. MT-Level: Safe if <dict> thread-safe. dictCreate(3) Returns a dictionary. If <threaded> is true, list is multi-thread safe. <root>, <maxLevel>, and <flushLimit> act as for skipNewList() (see skiplist.h) MT-Level... dictDestroy(3) Release all resources used by <dict>. MT-Level: Safe for unique <dict>. dictModifyValue(3) Finds <id>'s value and calls <update>. If <id> is not in <dict>, calls <new> to obtain a new value. MT-Level: Safe if <dict> thread-safe. dictNext(3) Can be used to iterate through values in the dictionary. The order is the order of the hash of the ids, which isn't usefully externally. Will return the value... dictReleaseLock(3) Releases the lock on the value associated with <lock>. Once the lock is released, the dictCleanupFunc callback can be called for the value (see dictCleanup())... dictRemove(3) Removes item identified by <id> from <dict>. MT-Level: Safe if <dict> thread-safe. dictSearch(3) Searches for <id> in <dict>, and returns value if found, or NULL if not. If <plock> is non-NULL, then the lock returned in <plock> will be associated with the... dictSetValue(3) Updates the <id>/<value> pair into <dict>. If <id> is not in <dict>, it is created. MT-Level: Safe if <dict> thread-safe. fCreate(3) Creates a file lock on named file <file>. The lock is returned in <plock>. MT-Level: Safe. fDestroy(3) Destroys the lock <lock> that was created by fCreate() or fFind(). MT-Level: Safe for unique <lock>. fFind(3) Find a file identified by the path <file>, and returns a lock identifier for it in <plock>. If the file doesn't exist, returns true. MT-Level: Safe. filter_create_fd(3) filter_create_fd and filter_create_fp are what popen been: a mechanism to create sub processes and have pipes to all their input/output. The concept was taken... filter_create_fp(3) filter_create_fp is identical to filter_create_fd, except each of the pipes is wrapped in a buffered stdio FILE filter_wait(3) filter_wait wraps the waitpid call and raises an error (with description) if the call failed. Note that if the ask for the exitcode and the process exited with... fLock(3) Acquires the lock identified by <lock>. This call blocks until the lock is acquired. MT-Level: Safe. fUnlock(3) Releases the lock identified by <lock>. MT-Level: Safe. hdf_copy(3) hdf_copy is a deep copy of an HDF tree pointed to by src to the named node of dest. dest and src need not be part of the same data set hdf_destroy(3) hdf_destroy is used to deallocate all memory associated with an hdf data set. Although you can pass an HDF node as an argument to this function, you are likely... hdf_dump(3) dump an HDF dataset to stdout Description: Input: Output: Returns: hdf_dump_str(3) dump an HDF dataset to STRING Description: Input: Output: Returns: hdf_get_child(3) hdf_get_child will walk the dataset starting at hdf to name, and return the first child of that node hdf_get_copy(3) hdf_get_copy is similar to hdf_get_value, except that it returns an malloc'd copy of the string. hdf_get_int_value(3) hdf_get_int_value walks the HDF data set pointed to by hdf to name, and returns the value of that node converted to an integer. If that node does not exist, or... hdf_get_node(3) hdf_get_node is similar to hdf_get_obj, except instead of stopping if it can't find a node in the tree, it will create all of the nodes necessary to hand you... hdf_get_obj(3) hdf_get_obj walks the dataset given by hdf to the node named name, and then returns the pointer to that node hdf_get_value(3) hdf_get_value walks the data set pointed to by hdf via name and returns the string value located there, or defval if the node doesn't exist hdf_get_valuef(3) hdf_get_valuef walks the data set pointed to by hdf via namefmt printf expanded with varargs, and returns the string value located there, or NULL if it doesn't... hdf_get_valuevf(3) hdf_get_valuevf walks the data set pointed to by hdf via namefmt printf expanded with varargs ap, and returns the string value located there, or NULL if it... hdf_init(3) hdf_init initializes an HDF data set and returns the pointer to the top node in the data set. hdf_obj_attr(3) Return the HDF Attributes for a node Description: Input: Output: Returns: hdf_obj_child(3) hdf_obj_child and the other hdf_obj_ functions are accessors to the HDF dataset. Although we do not currently "hide" the HDF struct implementation, we recommend... hdf_obj_name(3) hdf_obj_name is an accessor function for a datset node which returns the name of the node. This is just the local name, and not the full path. hdf_obj_top(3) hdf_obj_top is an accessor function which returns a pointer to the top of the dataset, the node which was returned by hdf_init. This is most useful for... hdf_obj_value(3) hdf_obj_value is an accessor function for a dataset node which returns the value of the node, or NULL if the node has no value. This is not a copy of the value... hdf_register_fileload(3) hdf_register_fileload registers a fileload function that overrides the built-in function. The built-in function uses hdf_search_path and ne_file_load (based on... hdf_remove_tree(3) delete a subtree of an HDF dataset Description: Input: Output: Returns: hdf_search_path(3) hdf_search_path is a convenience/utility function that searches for relative filenames in a search path. The search path is the list given by the children of... hdf_set_buf(3) hdf_set_buf is similar to hdf_set_value, except the dataset takes ownership of the value instead of making a copy of it. The dataset assumes that value was... hdf_set_copy(3) hdf_set_copy first walks the hdf dataset to the named src node, and then copies that value to the named dest node. If the src node is not found, an error is... hdf_set_int_value(3) hdf_set_int_value is a helper function that maps an integer to a string, and then calls hdf_set_value with that string hdf_set_symlink(3) hdf_set_symlink creates a link between two sections of an HDF dataset. The link is "by name" hence the term "symlink". This means that the destination node does... hdf_set_value(3) hdf_set_value will set the value of a named node. All of the interstitial nodes which don't exist will be created with a value of NULL. Existing nodes are not... hdf_set_valuef(3) hdf_set_valuef is a convenience function that wraps hdf_set_value. Due to limitations of C, the fmt is in the format "name=value", where we will first format... hdf_sort_obj(3) hdf_sort_obj will sort the children of an HDF node, based on the given comparison function. This function works by creating an array of the pointers for each... mCreate(3) Initializes the mutex <mutex>. MT-Level: Safe for unique <mutex>. mDestroy(3) Destroys the mutex <mutex> that was initialized by mCreate(). MT-Level: Safe for unique <mutex>. mLock(3) Locks the mutex <mutex>. This call blocks until the mutex is acquired. MT-Level: Safe. mUnlock(3) Unlocks the mutex <mutex>. MT-Level: Safe. nerr_error_string(3) returns the string associated with an error (the bottom level of the error chain) nerr_handle(3) nerr_handle is a convenience function. It is the equivalent of nerr_match, but it will also deallocate the error chain on a match. nerr_ignore(3) you should only call this if you actually handle the error (should I rename it?). Free's the error chain. nerr_init(3) initialize the NEOERR system. Can be called more than once. Is not thread safe. This registers all of the built in error types as defined at the top of this... nerr_log_error(3) currently, this prints out the error to stderr, and free's the error chain nerr_match(3) nerr_match is used to walk the NEOERR chain and match the error against a specific error type. In exception parlance, this would be the equivalent of "catch"... nerr_pass(3) this function is used to pass an error up a level in the call chain (ie, if the error isn't handled at the current level). This allows us to track the traceback... nerr_pass_ctx(3) this function is used to pass an error up a level in the call chain (ie, if the error isn't handled at the current level). This allows us to track the traceback... nerr_register(3) register an error type. This will assign a numeric value to the type, and keep track of the "pretty name" for it. skipDelete(3) Delete the item associated with <key> from <list>. MT-Level: Safe if <list> thread-safe. skipFreeList(3) Release all resources used by <list> including all key/value pairs. MT-Level: Safe for unique <list>. skipInsert(3) Inserts the <key>/<value> pair into the <list>. Key values 0 and -1 are reserved (and illegal). If key is already in list, and <allowUpdate> is true, value is... skipNewList(3) Returns a new skip list. If <threaded> is true, list is multi-thread safe. <root> and <maxLevel> determine performance and expected size (see discussion above)... skipNext(3) Searches in list <list> for item with key next larger that the one in <pkey>, and returns its value if found, or NULL if not. If <plock> is non-NULL, then the... skipRelease(3) Releases the lock on the value associated with <lock>. Once the lock is released, the freeValue callback can be called and the item freed (see skipNewList())... skipSearch(3) Searches for <key> in <list>, and returns value if found, or NULL if not. If <plock> is non-NULL, then the lock returned in <plock> will be associated with the... wdb_keys(3) this function returns the key and column names for the current database