Searched refs:format (Results 76 - 100 of 159) sorted by relevance

1234567

/barrelfish-2018-10-04/include/openssl/
H A Dbio.h684 int BIO_printf(BIO *bio, const char *format, ...)
686 int BIO_vprintf(BIO *bio, const char *format, va_list args)
688 int BIO_snprintf(char *buf, size_t n, const char *format, ...)
690 int BIO_vsnprintf(char *buf, size_t n, const char *format, va_list args)
/barrelfish-2018-10-04/lib/cxx/include/
H A Dlibunwind.h83 uint32_t format; /* compact unwind encoding, or zero if none */ member in struct:unw_proc_info_t
104 /* Save VFP registers in FSTMX format (instead of FSTMD). */
/barrelfish-2018-10-04/usr/tests/rpc_cap_test/
H A Drpc_cap_test.c27 __attribute__((format(printf, 1, 2)))
/barrelfish-2018-10-04/lib/tzcode/zic/
H A Dzic.c114 static void doabbr(char * abbr, const char * format,
423 ** Match the format of "cc" to allow sh users to
791 ** a '%s' in the format is a bad thing.
1057 error(_("invalid abbreviation format"));
1751 doabbr(abbr, format, letters, isdst, doquotes)
1753 const char * const format;
1762 slashp = strchr(format, '/');
1765 (void) strcpy(abbr, format);
1766 else (void) sprintf(abbr, format, letters);
1770 if (slashp > format)
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/src/
H A Dbip_misc.c536 char *s, *format; local
542 format = StringStart(vformat);
545 format = DidName(vformat.did);
548 format = DidName(d_.nil);
568 len = strftime((char *) BufferStart(pw), max+1, format, &time_here);
H A Dwrite.c674 * ATTRIBUTE print attributes of metaterms in user format
675 * STD_ATTR print attributes of metaterms in standard format
1968 * deal better with errors that occur halfway through the format string.
1971 * the remaining format string in vse/tse
1985 char *format, *cpar, *npar, par[32]; local
1997 Get_Name(strval, strtag, format);
2020 par[0] = '%'; /* here we build up the format string for C printf */
2024 last_format = format;
2028 for (; *format; last_format = ++format, last_lis
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/applications/
H A Dtutorial.tex109 The tutorial follows a top-down methodology for the design of an application. Chapter~\ref{highleveldesign} discusses general issues of modular design and self-documenting code for ECLiPSe programs. The next chapter on data structures compares different ways of representing data internally and externally, and presents a canonical multi-representation format which allows effective access to data in all parts of an application. Chapter~\ref{gettingittowork} shows how to convert a high level specification into an executable program early in the development stage. The bulk of the tutorial is contained in chapter~\ref{programmingconcepts}, where we present a number of different programming concepts which can be used as development templates to solve particular problems. This is followed by chapter~\ref{inputoutput} on input/output, a particularly important aspect of developing extensible programs. The last two chapters deal with debugging (chapter~\ref{ifitdoesntwork}) and testing (chapter~\ref{correctnessandperformance}).
164 Examples of the first type (see figure~\ref{fullapplication}) are Parc Technologies applications (http://www.parc-technologies.com) like AirPlanner\index{AirPlanner} and RiskWise\index{RiskWise}\footnote{In the following we use a number of examples from the RiskWise application. It is a network analysis tool for IP networks, which uses a constraint solver to determine traffic pattern in the network. If this doesn't make any sense to you, relax. An understanding of the networking application domain is not required to follow this tutorial.}, where everything except the problem solver is developed in Java\index{Java} or related tools. The interface between the main application and the problem solver written in ECLiPSe is via a Java-ECLiPSe interface. In this interface, the main application poses queries for the ECLiPSe solver, passing data and arguments into ECLiPSe. The problem solver then runs the query and returns results as variable bindings in the given query. The Java side only knows about these queries, their data format and the expected results. The internals of the solver, how the queries are resolved, is completely hidden. This defines a nice interface between the application parts, as long as the queries are well defined and documented. Once that design is frozen, the developers for the different parts can continue development independently from each other, using stubs or dummy routines to simulate the other application parts.
171 The critical issue in defining the queries lies in identifying which data are required and/or produced, without building an actual implementation of the system. Another issue is the format of the data, which should allow a simple and efficient implementation without extra overhead for data manipulation. It is most important to get this interface right from the start, as any change will create re-work and problems integrating different versions of the software.
430 \item[data files] The second alternative is to use data files in a fixed format. The ECLiPSe program then has to read these files and build the internal data structures at the same time. Depending on the format, this may require parsing the input format with definite clause grammars (DCG) \index{DCG}\index{definite clause grammar}(see section \ref{howtousedcgs}), adding to the development effort\footnote{ECLiPSEe 5.4 contains a freeware XML (http://www.xml.org) parser which handles most of the detail of parsing XML files. This makes the use of XML as a data exchange format for ECLiPSe are very exiting new possibility. The parser is described in the ``Third Party Library'' section of the reference manual.}. But as the files can be read and written easily, it is quite simple to create test data sets and to analyze problems by hand. The design for the fixed format may require some extra effort if we want to use the full character set for atoms and strings. A proper quoting mechanism may be required in order to distinguish say a comma separator from a comma contained inside a data field.
432 \item[prolog terms] The third alternative is to use data files as before, but to format them as valid Prolog terms \index{Prolog term}that can directly read with the ECLiPSe term I/O predicates. This avoids the overhead of writing parsers in ECLiPSe, but may be difficult for the calling side of the application, unless that is also written in ECLiPSe. Note that we again may face quoting problems, in particular for single and double quotes.
434 \item[EXDR] ECLiPSe also provides a binary data format calle
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/
H A Ddatabase-lst.tex47 \item[?RelationName \hspace{1mm} $<$=$>$ \hspace{1mm} ?SpecList)]{Create or remove a relation. Query relation format.}
H A Dknowbase-lst.tex44 \item[?RelationName \hspace {1mm} $<$==$>$ \hspace {1mm} ?SpecList)]{Create or remove a relation. Query relation format.}
/barrelfish-2018-10-04/kernel/arch/armv7/
H A Dpaging.c23 #define MSG(format, ...) printk( LOG_NOTE, "ARMv7-A: "format, ## __VA_ARGS__ )
H A Dstartup_arch.c43 #define MSG(format, ...) printk( LOG_NOTE, "ARMv7-A: "format, ## __VA_ARGS__ )
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/
H A Ddevelopment_support.pl113 printf(error, "ERROR: unrecognised format for structure field index: %w in %w.%n", [Name0,Defs0]),
182 % Output mode format character codes
H A Dtoplevel.pl51 % in exdr-format:
57 % string in <exdr>-format, and is one of:
64 % Variable bindings will be printed (in no particular format)
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/
H A Dembvb.tex224 See chapter \ref{chapexdr} for details about EXDR format.
229 See chapter \ref{chapexdr} for details about EXDR format.
H A Dembremote.tex171 \item[\index{ec_remote_init (Tcl remote interface)}{\bf ec_remote_init} {\it host port ?init_command? ?pass? ?format?}]\ \\
179 details). {\it pass\/} and {\it format\/} are optional arguments for a simple
183 will be sent to the {\eclipse} side in EXDR format\footnote{See
184 section~\ref{secexdrtcl} for more on EXDR format}; the default is
272 \item[\index{ec_rpc (Tcl remote interface)}{\bf ec_rpc} {\it goal ?format?}]\ \\
282 If no format argument is given, the goal is assumed to be in
283 {\eclipse} syntax. If a {\it format} argument is provided,
284 the {\eclipse} goal is constructed from {\it goal} and {\it format},
288 goal as a Tcl data structure (in EXDR format), otherwise "fail" or
301 be in EXDR format, i
[all...]
H A Ddbi.tex81 If the database has a generic binary format, such as Binary Long Object
86 be converted to EXDR data interchange format (see the Embedding and
195 be stored or retrieved in external database format. This way one is not
233 database, then the term should be first converted to EXDR format, and the
265 in external database format. Any structure whose first argument is an integer
H A Dembremoteproto.tex55 chapter~\ref{chapexdr}) format according to the protocol. This allows the
69 interface. Messages (in EXDR format) are sent in both directions according
72 to {\eclipse} and return the results. The goal is sent in EXDR format.
91 {\eclipse} goal, in EXDR format to be executed by the {\eclipse} side. This
183 control socket in EXDR format and flush it. This should be a {\tt
197 \item Remote side: write the `pass-term' in EXDR format on the newly created control
207 connection. This is sent in EXDR format, and is used to identify this
212 format, and the connection flushed.
222 newly established ec_rpc connection. This is also sent in EXDR format. This
486 control connection, and are in EXDR format
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/tutorial/
H A Deprolog.tex301 write one term in a default format.
303 write one term, format options can be selected.
305 write a string with embedded terms, according to a format string.
324 The write-format is the shortest, but some information is missing,
326 is a string and not an atom. The writeq-format quotes items properly,
385 \eclipse{}-specific format extensions.
403 The most important \eclipse{}-specific format option is \%w, which
409 The \%w format allows a number of modifiers in order to access all the
/barrelfish-2018-10-04/include/
H A Dzlib.h26 The data format used by the zlib library is described by RFCs (Request for
28 (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format).
56 The compressed data format used by default by the in-memory functions is
57 the zlib format, which is a zlib wrapper documented in RFC 1950, wrapped
60 The library also supports reading and writing files in gzip (.gz) format
62 with "gz". The gzip format is different from the zlib format. gzip is a
67 The zlib format wa
[all...]
/barrelfish-2018-10-04/lib/openssl-1.0.0d/ssl/
H A Dssl_ciph.c1460 static const char *format="%-23s %s Kx=%-8s Au=%-4s Enc=%-9s Mac=%-4s%s AL=%lx/%lx/%lx/%lx/%lx\n"; local
1462 static const char *format="%-23s %s Kx=%-8s Au=%-4s Enc=%-9s Mac=%-4s%s\n"; local
1613 BIO_snprintf(buf,len,format,cipher->name,ver,kx,au,enc,mac,exp_str,alg_mkey,alg_auth,alg_enc,alg_mac,alg_ssl);
1615 BIO_snprintf(buf,len,format,cipher->name,ver,kx,au,enc,mac,exp_str);
/barrelfish-2018-10-04/lib/devif/backends/net/mlx4/drivers/infiniband/hw/mlx4/
H A Dmcg.c49 #define mcg_warn_group(group, format, arg...) \
50 pr_warn("%s-%d: %16s (port %d): WARNING: " format, __func__, __LINE__,\
53 #define mcg_error_group(group, format, arg...) \
54 pr_err(" %16s: " format, (group)->name, ## arg)
/barrelfish-2018-10-04/lib/xeon_phi/
H A Dxeon_phi_client.c992 static char* format = "%s { domid: _ }";
993 int length = snprintf(NULL, 0, format, iface);
999 snprintf(query, length + 1, format, iface);
/barrelfish-2018-10-04/usr/skb/programs/
H A Dirq_routing_new.pl87 % It must take care of ensuring the OutMsg has the right format, either a
344 % Same format as produced from route(..).
355 % The format of a line is:
358 % follows the format
764 % This function prints a CSV file in the following format:
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/
H A Dumsopsys.tex224 The file names used by {\eclipse} is in the Unix format, including on Window
230 the conversion between the format used in {\eclipse} and the Operating
231 Systems' format.
/barrelfish-2018-10-04/tools/arm_boot/
H A Darm_bootimage.c45 #define DBG(format, ...) printf(format, ## __VA_ARGS__)
47 #define DBG(format, ...)

Completed in 175 milliseconds

1234567