features
DIScover
files
impact options
filter
saving
filter set scores
filtering
entity subsets
query results
Basic Filtering
Filtering Results
advanced
finding
a group
flow chart
opening
function impact options
generating
an impact analysis
an impact analysis report
generating impact reports
globalization
queries
Graph
view
graphic symbols
call tree
inheritance view
graphical views
call graph
data chart
entity relation diagram
flow chart
general options
inheritance
outline
source code
tree diagram
graphics
described
group
adding entities
creating
deleting
described
exporting contents
finding
operations
removing entities
searching
viewing contents
working with
groups
dormant-code-auto-nnn
working with in Developer Xpress
Groups pane
described
gVim
choosing
using
header files
simplifying
hits
described
icons
described
IDE
choosing
managing source code changes
post-installation
IDEs
Developer Xpress
choosing
Emacs
using
gVim
using
launching
Microsoft Visual Studio
using
impact analysis
benefits
described
Java language options
options
C/C++
Java
performing
report
attaching to issues
generating
printing
saving
reports
information model
connecting to
described
inheritance view
color codes
expert mode
graphic symbols
menu options
opening
installing DIScover
uninstalling
instance
described
instances
viewing
Integrity Manager integration
described
setting up
interface
model browser
interface impact options
issues
attaching impact analysis reports to
attaching quality assessment reports
Java
impact analysis options
JBuilder
launching
an IDE
Developer Xpress
list filtering
local variable impact options
locating
unused entities
logical symbols
entity relation diagram
macro impact options
making queries
member status (classes)
methods
impact options
metric queries
metrics
creating a complex query
described
displaying
Displaying Metrics
To display metrics with an entity in a column
Filter Setup dialog box
list of
Microsoft Visual Studio
choosing
using
mini-buffer
model browser
Categories pane
described
graphics
Groups pane
icons
interface
described
mouse operations
Projects pane
Queries pane
Results window
starting
model environment
described
model server
described
Developer Xpress
choosing
model version
connecting to
mouse operations
navigating
source code
in Developer Xpress
nested entity types
nested structures
entity types
notation
No Transform
source mode option
notation
nested structures
open definition
opening
a call graph
a data chart
a flow chart
a tree diagram
an entity relation diagram
an IDE
an inheritance view
an outline view
options
data chart
entity relation diagram
inheritance view
tree diagram
outline view
opening


PolyglotMan(1) PolyglotMan(1) NAME PolyglotMan, rman - reverse compile man pages from formatted form to a number of source formats: ASCII, roff, TkMan, Tk, Sections, HTML, SGML, MIME, LaTeX, LaTeX2e, RTF, POD. SYNOPSIS rman [ options ] [ file ] DESCRIPTION Up-to-date instructions can be found at http://polyglotman.source‐ forge.net/rman.html PolyglotMan takes man pages from most of the popular flavors of UNIX and transforms them into any of a number of text source formats. PolyglotMan was formerly known as RosettaMan. The name of the binary is still called rman, for scripts that depend on that name; mnemonically, just think "reverse man". Previously PolyglotMan required pages to be formatted by nroff(1) prior to its processing. With version 3.0, it prefers [tn]roff source and usually produces results that are better yet. And source pro‐ cessing is the only way to translate tables. Source format translation is not as mature as formatted, however, so try formatted translation as a backup. In parsing [tn]roff source, one could implement an arbitrarily large sub‐ set of [tn]roff, which I did not and will not do, so the results can be off. I did implement a significant subset of those used in man pages, however, including tbl (but not eqn), if tests, and general macro defini‐ tions, so usually the results look great. If they don't, format the page with nroff before sending it to PolyglotMan. If PolyglotMan doesn't rec‐ ognize a key macro used by a large class of pages, however, e-mail me the source and a uuencoded nroff-formatted page and I'll see what I can do. When running PolyglotMan with man page source that includes or redirects to other [tn]roff source using the .so (source or inclusion) macro, you should be in the parent directory of the page, since pages are written with this assumption. For example, if you are translating /usr/share/man/man1/ls.1, first cd into /usr/share/man. PolyglotMan accepts man pages from: SunOS, Sun Solaris, Hewlett-Packard HP-UX, AT&T System V, OSF/1 aka Digital UNIX, DEC Ultrix, SGI IRIX, Linux, FreeBSD, SCO. Source processing works for: SunOS, Sun Solaris, Hewlett-Packard HP-UX, AT&T System V, OSF/1 aka Digital UNIX, DEC Ultrix. It can produce printable ASCII-only (control characters stripped), sec‐ tion headers-only, Tk, TkMan, [tn]roff (traditional man page source), XML, HTML, MIME, LaTeX, LaTeX2e, RTF, Perl 5 POD. A modular architecture permits easy addition of additional output formats. The latest version of PolyglotMan is available from http://polyglot‐ man.sourceforge.net/ . OPTIONS The following options should not be used with any others and exit Poly‐ glotMan without processing any input. -h|--help Show list of command line options and exit. -v|--version Show version number and exit. You should specify the filter first, as this sets a number of parameters, and then specify other options. -f|--filter <ASCII|roff|TkMan|Tk|Sec‐ tions|HTML|XML|MIME|LaTeX|LaTeX2e|RTF|POD> Set the output filter. Defaults to ASCII. -S|--source PolyglotMan tries to automatically determine whether its input is source or formatted; use this option to declare source input. -F|--format|--formatted PolyglotMan tries to automatically determine whether its input is source or formatted; use this option to declare formatted input. -l|--title printf-string In HTML mode this sets the <TITLE> of the man pages, given the same parameters as -r . -r|--reference|--manref printf-string In HTML and XML modes this sets the URL form by which to retrieve other man pages. The string can use two supplied parameters: the man page name and its section. (See the Examples section.) If the string is null (as if set from a shell by "-r ''"), `-' or `off', then man page refer‐ ences will not be HREFs, just set in italics. If your printf supports XPG3 positions specifier, this can be quite flexible. -V|--volumes <colon-separated list> Set the list of valid volumes to check against when look‐ ing for cross-references to other man pages. Defaults to 1:2:3:4:5:6:7:8:9:o:l:n:p (volume names can be multichar‐ acter). If an non-whitespace string in the page is immedi‐ ately followed by a left parenthesis, then one of the valid volumes, and ends with optional other characters and then a right parenthesis--then that string is reported as a reference to another manual page. If this -V string starts with an equals sign, then no optional characters are allowed between the match to the list of valids and the right parenthesis. (This option is needed for SCO UNIX.) The following options apply only when formatted pages are given as input. They do not apply to or are always handled correctly with the source. -b|--subsections Try to recognize subsection titles in addition to section titles. This can cause problems on some UNIX flavors. -K|--nobreak Indicate manual pages don't have page breaks, so don't look for footers and headers around them. (Older nroff -man macros always put in page breaks, but lately some vendors have realized that printouts are made through troff(1), whereas nroff -man is used to format pages for reading on screen, and so have eliminated page breaks.) PolyglotMan usually gets this right even without this flag. -k|--keep Keep headers and footers, as a canonical report at the end of the page. changeleft Move changebars, such as those found in the Tcl/Tk manual pages, to the left. --> notag‐ gressive Disable aggressive man page parsing. Aggressive manual, which is on by default, page parsing elides head‐ ers and footers, identifies sections and more. --> -n|--name name Set name of man page (used in roff format). If the file‐ name is given in the form " name . section ", the name and section are automatically determined. If the page is being parsed from [tn]roff source and it has a .TH line, this information is extracted from that line. -p|--paragraph paragraph mode toggle. The filter determines whether lines should be linebroken as they were by nroff, or whether lines should be flowed together into paragraphs. Mainly for internal use. -s|section # Set volume (aka section) number of man page (used in roff format). tables Turn on aggressive table parsing. --> -t|--tabstops # For those macros sets that use tabs in place of spaces where possible in order to reduce the number of characters used, set tabstops every # columns. Defaults to 8. NOTES ON FILTER TYPES ROFF Some flavors of UNIX ship man page without [tn]roff source, making one's laser printer little more than a laser-powered daisy wheel. This filter tries to intuit the original [tn]roff directives, which can then be recompiled by [tn]roff. TkMan TkMan(1), a hypertext man page browser, uses PolyglotMan to show man pages without the (usually) useless headers and footers on each page. It also collects section and (optionally) subsection heads for direct access from a pulldown menu. TkMan and Tcl/Tk, the toolkit in which it's writ‐ ten, are available via anonymous ftp from ftp://ftp.smli.com/pub/tcl/ Tk This option outputs the text in a series of Tcl lists consisting of text- tags pairs, where tag names roughly correspond to HTML. This output can be inserted into a Tk text widget by doing an eval <textwidget> insert end <text> . This format should be relatively easily parsible by other programs that want both the text and the tags. See also ASCII. ASCII When printed on a line printer, man pages try to produce special text effects by overstriking characters with themselves (to produce bold) and underscores (underlining). Other text processing software, such as text editors, searchers, and indexers, must counteract this. The ASCII filter strips away this formatting. Piping nroff output through col -b also strips away this formatting, but it leaves behind unsightly page headers and footers. Also see Tk. Sections Dumps section and (optionally) subsection titles. This might be useful for another program that processes man pages. HTML With a simple extension to a HTTP server for Mosaic(1) or other World Wide Web browser, PolyglotMan can produce high quality HTML on the fly. Several such extensions and pointers to several others are included in PolyglotMan 's contrib directory. XML This is appoaching the Docbook DTD, but I'm hoping that someone with a real interest in this will polish the tags generated. Try it to see how close the tags are now. MIME MIME (Multipurpose Internet Mail Extensions) as defined by RFC 1563, good for consumption by MIME-aware e-mailers or as Emacs (>=19.29) enriched documents. LaTeX and LaTeX2e Why not? RTF Use output on Mac or NeXT or whatever. Maybe take random man pages and integrate them better with NeXT's documentation system. Maybe NeXT has its own man page macros that do this. PostScript and FrameMaker To produce PostScript, use groff or psroff . To produce FrameMaker MIF, use FrameMaker's builtin filter. In both cases you need [tn]roff source, so if you only have a formatted version of the manual page, use Polyglot‐ Man 's roff filter first. EXAMPLES To convert the formatted man page named ls.1 back into [tn]roff source form: rman -f roff /usr/local/man/cat1/ls.1 > /usr/local/man/man1/ls.1 Long man pages are often compressed to conserve space (compression is especially effective on formatted man pages as many of the characters are spaces). As it is a long man page, it probably has subsections, which we try to separate out (some macro sets don't distinguish subsections well enough for PolyglotMan to detect them). Let's convert this to LaTeX for‐ mat: pcat /usr/catman/a_man/cat1/automount.z | rman -b -n automount -s 1 -f latex > automount.man Alternatively, man 1 automount | rman -b -n automount -s 1 -f latex > automount.man For HTML/Mosaic users, PolyglotMan can, without modification of the source code, produce HTML links that point to other HTML man pages either pregenerated or generated on the fly. First let's assume pregenerated HTML versions of man pages stored in /usr/share/man/html . Generate these one-by-one with the following form: rman -f html -r 'http:/usr/share/man/html/%s.%s.html' /usr/share/man/cat1/ls.1 > /usr/share/man/html/ls.1.html If you've extended your HTML client to generate HTML on the fly you should use something like: rman -f html -r 'http:~/bin/man2html?%s:%s' /usr/share/man/cat1/ls.1 when generating HTML. BUGS/INCOMPATIBILITIES PolyglotMan is not perfect in all cases, but it usually does a good job, and in any case reduces the problem of converting man pages to light editing. Tables in formatted pages, especially H-P's, aren't handled very well. Be sure to pass in source for the page to recognize tables. The man pager woman(1) applies its own idea of formatting for man pages, which can confuse PolyglotMan . Bypass woman by passing the formatted manual page text directly into PolyglotMan . The [tn]roff output format uses fB to turn on boldface. If your macro set requires .B, you'll have to a postprocess the PolyglotMan output. SEE ALSO tkman(1) , xman(1) , man(1) , man(7) or man(5) depending on your flavor of UNIX AUTHOR PolyglotMan by Thomas A. Phelps<EMAIL_ADDRESS>) developed at the University of California, Berkeley Computer Science Division Manual page last updated on $Date: 1998/07/13 09:47:28 $ PolyglotMan(1)


Legend
Unread
High Priority
Medium Priority
Low Priority
Unread
High Priority
Medium Priority
Low Priority
© 2005-2020 IMVU
|
Advertise |
Terms of Service |
Privacy |
Code of Conduct |
Upload Policy
50070 Users online —
1719 guests,
16681 registered
and 31670 other
Limit bot activity to periods with less than 10k registered users online.
Server Time: Nov 4, 2020 03:01 PM
This website uses cookies to enhance your browsing experience. Learn More


Local Biodiversity Strategy and Action Plan Guidelines:
an aid to municipal planning and biodiversity conservation
The
Local Biodiversity Strategy and Action Plan Guidelines: an aid to municipal planning and biodiversity conservation are intended to assist local governments in making a start with, or improvements to, their biodiversity planning processes. Drawing from local government experiences and examples, the Guidelines provide background guidance and supporting information for biodiversity strategy and action planning at the local level. Published as a working document, we intend to continuously add to and fine-tune the Guidelines, creating an increasingly comprehensive and interactive tool. Once you have downloaded the publication free of charge by clicking on the picture, below, please consider doing the following:
1. Using the Guidelines to support local planning within your local government
2. Providing suggestions on how the Guidelines can be improved
Please send your specific comments or case studies to biodiversity[at]iclei.org.


KafkaConfig
public class KafkaConfig
The configuration settings for a Kafka consumer/producer.
These can be set either using the helper functions provided or
by subscripting KafkaConfig
with the configuration key.
Link to configuration keys and descriptions.
Usage Example:
let config = KafkaConfig()
config.groupId = "Kitura"
let producer = try? KafkaConsumer(config: config)
-
The internal representation of the Kafka configuration.
Values can be set by subscriptingKafkaConfig
directly.Declaration
Swift
public internal(set) var dictionary = [String: String]()
-
Initialize a KafkaConfig instance with default settings.
Declaration
Swift
public init()
-
Directly set the configuration settings for librdKafka.
Link to configuration keys and descriptions.Declaration
Swift
public subscript(key: String) -> String?
-
Client identifier. Defaults to
rdkafka
.Declaration
Swift
public var clientID: String
-
Maximum Kafka protocol request message size. Defaults to 1000000.
Declaration
Swift
public var messageMaxBytes: Int
-
Maximum size for message to be copied to buffer. Messages larger than this will be passed by reference (zero-copy) at the expense of larger iovecs. Defaults to 65535.
Declaration
Swift
public var messageCopyMaxBytes: Int
-
Maximum Kafka protocol response message size. This serves as a safety precaution to avoid memory exhaustion in case of protocol hickups. This value must be at least fetchMaxBytes + 512 to allow for protocol overhead; the value is adjusted automatically unless the configuration property is explicitly set. Defaults to 100000000.
Declaration
Swift
public var receiveMessageMaxBytes: Int
-
Maximum number of in-flight requests per broker connection. This is a generic property applied to all broker communication, however it is primarily relevant to produce requests. In particular, note that other mechanisms limit the number of outstanding consumer fetch request per broker to one. Defaults to 1000000
Declaration
Swift
public var maxInFlightRequestsPerConnection: Int
-
Non-topic request timeout in milliseconds. This is for metadata requests, etc. Defaults to 60000.
Declaration
Swift
public var metadataRequestTimeoutMs: Int
-
Topic metadata refresh interval in milliseconds. The metadata is automatically refreshed on error and connect. Use -1 to disable the intervalled refresh. Defaults to 300000
Declaration
Swift
public var topicMetadataRefreshIntervalMs: Int
-
Metadata cache max age. Defaults to topic.metadata.refresh.interval.ms * 3
Declaration
Swift
public var metadataMaxAgeMs: Int
-
When a topic loses its leader a new metadata request will be enqueued with this initial interval, exponentially increasing until the topic metadata has been refreshed. This is used to recover quickly from transitioning leader brokers. Defaults to 250.
Declaration
Swift
public var topicMetadataRefreshFastIntervalMs: Int
-
Sparse metadata requests (consumes less network bandwidth). Defaults to true.
Declaration
Swift
public var topicMetadataRefreshSparse: Bool
-
An array of debug contexts to enable. Defaults to an empty array.
Declaration
Swift
public var debug: [DebugOptions]
-
The possible debug options that can be enabled.
See moreDeclaration
Swift
public struct DebugOptions: CustomStringConvertible
-
Default timeout for network requests.
Producer: ProduceRequests will use the lesser value of socket.timeout.ms and remaining message.timeout.ms for the first message in the batch.
Consumer: FetchRequests will use fetch.wait.max.ms + socket.timeout.ms. Admin: Admin requests will use socket.timeout.ms
Defaults to 60000.Declaration
Swift
public var socketTimeoutMs: Int
-
Broker socket send buffer size. System default is used if 0. Defaults to 0.
Declaration
Swift
public var socketSendBufferBytes: Int
-
Broker socket receive buffer size. System default is used if 0. Defaults to 0.
Declaration
Swift
public var socketReceiveBufferBytes: Int
-
Enable TCP keep-alives (SO_KEEPALIVE) on broker sockets. Defaults to false
Declaration
Swift
public var socketKeepaliveEnable: Bool
-
Disable the Nagle algorithm (TCP_NODELAY) on broker sockets.
Declaration
Swift
public var socketNagleDisable: Bool
-
Disconnect from broker when this number of send failures (e.g., timed out requests) is reached. Disable with 0. WARNING: It is highly recommended to leave this setting at its default value of 1 to avoid the client and broker to become desynchronized in case of request timeouts. NOTE: The connection is automatically re-established.
Declaration
Swift
public var socketMaxFails: Int
-
Allowed broker
IPAddressFamily
(any, IPv4, IPv6). Defaults toany
.Declaration
Swift
public var brokerAddressFamily: IPAddressFamily
-
The possible IP address family options that can be set.
See moreDeclaration
Swift
public struct IPAddressFamily: CustomStringConvertible
-
The initial time to wait before reconnecting to a broker after the connection has been closed. The time is increased exponentially until reconnect.backoff.max.ms is reached. -25% to +50% jitter is applied to each reconnect backoff. A value of 0 disables the backoff and reconnects immediately. Defaults to 100.
Declaration
Swift
public var reconnectBackoffMs: Int
-
The maximum time to wait before reconnecting to a broker after the connection has been closed. Defaults to 10000.
Declaration
Swift
public var reconnectBackoffMaxMs: Int
-
The
SecurityProtocol
used to communicate with brokers.Declaration
Swift
public var securityProtocol: SecurityProtocol
-
The possible security protocols that can be used to communicate with brokers.
See moreDeclaration
Swift
public struct SecurityProtocol: CustomStringConvertible
-
Path to client’s private key (PEM) used for authentication. Defaults to nil.
Declaration
Swift
public var sslKeyLocation: String?
-
Private key passphrase. Defaults to nil.
Declaration
Swift
public var sslKeyPassword: String?
-
Path to client’s public key (PEM) used for authentication. Defaults to nil.
Declaration
Swift
public var sslCertificateLocation: String?
-
File or directory path to CA certificate(s) for verifying the broker’s key. Defaults to nil.
Declaration
Swift
public var sslCaLocation: String?
-
Path to CRL for verifying broker’s certificate validity. Defaults to nil.
Declaration
Swift
public var sslCrlLocation: String?
-
Path to client’s keystore (PKCS#12) used for authentication. Defaults to nil.
Declaration
Swift
public var sslKeystoreLocation: String?
-
Client’s keystore (PKCS#12) password. Defaults to nil.
Declaration
Swift
public var sslKeystorePassword: String?
-
SASL mechanism to use for authentication. Defaults to GSSAPI.
Declaration
Swift
public var saslMechanism: SASLMechanism
-
The possible SASL mechanisms that can be used for authentication.
See moreDeclaration
Swift
public struct SASLMechanism: CustomStringConvertible
-
SASL username for use with the PLAIN, SCRAM-SHA-256 and SCRAM-SHA-512 mechanisms. Defaults to nil.
Declaration
Swift
public var saslUsername: String?
-
SASL password for use with the PLAIN, SCRAM-SHA-256 and SCRAM-SHA-512 mechanisms. Defaults to nil.
Declaration
Swift
public var saslPassword: String?
-
Consumer Only. Client group id string. All clients sharing the same group.id belong to the same group and the messages will be split between them. Defaults to nil, meaning a random UUID String will be used as the groupId.
Declaration
Swift
public var groupId: String?
-
Consumer Only. Client group session and failure detection timeout. The consumer sends periodic heartbeats (heartbeat.interval.ms) to indicate its liveness to the broker. If no hearts are received by the broker for a group member within the session timeout, the broker will remove the consumer from the group and trigger a rebalance. Defaults to 10000.
Declaration
Swift
public var sessionTimeoutMs: Int
-
Consumer Only. Group session keepalive heartbeat interval. Defaults to 3000.
Declaration
Swift
public var heartbeatIntervalMs: Int
-
Consumer Only. Maximum allowed time between calls to consume messages (e.g., rd_kafka_consumer_poll()) for high-level consumers. If this interval is exceeded the consumer is considered failed and the group will rebalance in order to reassign the partitions to another consumer group member. Warning: Offset commits may be not possible at this point. Note: It is recommended to set enable.auto.offset.store=false for long-time processing applications and then explicitly store offsets (using offsets_store()) after message processing, to make sure offsets are not auto-committed prior to processing has finished. The interval is checked two times per second. Defaults to 300000.
Declaration
Swift
public var maxPollIntervalMs: Int
-
Consumer Only. Automatically and periodically commit offsets in the background. Note: setting this to false does not prevent the consumer from fetching previously committed start offsets. To circumvent this behaviour set specific start offsets per partition in the call to assign(). Defaults to true.
Declaration
Swift
public var enableAutoCommit: Bool
-
Consumer Only. The frequency in milliseconds that the consumer offsets are committed (written) to offset storage. (0 = disable). Default to 5000.
Declaration
Swift
public var autoCommitIntervalMs: Int
-
Consumer Only. Automatically store offset of last message provided to application. The offset store is an in-memory store of the next offset to (auto-)commit for each partition. Defaults to true
Declaration
Swift
public var enableAutoOffsetStore: Bool
-
Consumer Only. Emit RD_KAFKA_RESP_ERR__PARTITION_EOF event whenever the consumer reaches the end of a partition. defaults to true.
Declaration
Swift
public var enablePartitionEOF: Bool
-
Producer only. When set to true, the producer will ensure that messages are successfully produced exactly once and in the original produce order. The following configuration properties are adjusted automatically (if not modified by the user) when idempotence is enabled: max.in.flight.requests.per.connection=5 (must be less than or equal to 5), retries=INT32_MAX (must be greater than 0), acks=all, queuing.strategy=fifo. Producer instantation will fail if user-supplied configuration is incompatible. Defaults to false.
Declaration
Swift
public var enableIdempotence: Bool
-
Producer only. Maximum number of messages allowed on the producer queue. This queue is shared by all topics and partitions. Defaults to 100000.
Declaration
Swift
public var queueBufferingMaxMessages: Int
-
Producer only. Maximum total message size sum allowed on the producer queue. This queue is shared by all topics and partitions. This property has higher priority than queue.buffering.max.messages. Defaults to 1048576.
Declaration
Swift
public var queueBufferingMaxKBytes: Int
-
Producer only. Delay in milliseconds to wait for messages in the producer queue to accumulate before constructing message batches (MessageSets) to transmit to brokers. A higher value allows larger and more effective (less overhead, improved compression) batches of messages to accumulate at the expense of increased message delivery latency. Defaults to 0.
Declaration
Swift
public var queueBufferingMaxMs: Int
-
Producer only. How many times to retry sending a failing Message. Note: retrying may cause reordering unless enable.idempotence is set to true. Defaults to 2.
Declaration
Swift
public var messageSendMaxRetries: Int
-
Producer only. This field indicates the number of acknowledgements the leader broker must receive from ISR brokers before responding to the request: 0=Broker does not send any response/ack to client, -1=Broker will block until message is committed by all in sync replicas (ISRs). Defaults to -1.
Declaration
Swift
public var requestRequiredAcks: Int
-
Producer only. The ack timeout of the producer request in milliseconds. This value is only enforced by the broker and relies on request.required.acks being != 0. Default 5000.
Declaration
Swift
public var requestTimeoutMs: Int
-
Producer only. Local message timeout. This value is only enforced locally and limits the time a produced message waits for successful delivery. A time of 0 is infinite. This is the maximum time Kitura-Kafka may use to deliver a message (including retries). Delivery error occurs when either the retry count or the message timeout are exceeded. Defaults to 300000.
Declaration
Swift
public var messageTimeoutMs: Int
-
Consumer only. Action to take when there is no initial offset in offset store or the desired offset is out of range: ‘smallest’,‘earliest’, ‘beginning’ - automatically reset the offset to the smallest offset, ‘largest’,‘latest’, ‘end’ - automatically reset the offset to the largest offset, ‘error’ - trigger an error which is retrieved by consuming message. Defaults to largest.
Declaration
Swift
public var autoOffsetReset: AutoResetOptions
-
A struct representing the options actions to take when there is no initial offset in offset store or the desired offset is out of range.
See moreDeclaration
Swift
public struct AutoResetOptions: CustomStringConvertible


Your browser does not supprt Canvas!
Game Over!
Level:
Easy
Not so easy
Hard
Bring it on!
Score:
0
Reset


THIRTEEN DAYS A film review by James Brundage Copyright 2000 filmcritic.com filmcritic.com
That's it. The nostalgia trip is heading for a long walk off of a short pier. I mean, really, who pitched this movie, and how did they pull it off?  Or, "It's potential nuclear holocaust... with a heart." And, if I didn't know the answer to the question of what moronic producer would buy the rights to the project (I'll give you a hint: he's also the film's biggest star), I'd ask that, too.
Thirteen Days, the second film of 2000 to do a number on the Massachusetts accent (really, you should hear Costner, he sounds like a drunk New Jerseyite), deals with a time period of 13 days during which we almost destroyed the world. No, it's not Crimson Tide, Part 2. It's the Cuban Missle Crisis, and it's presented here to us by the incapable hands of director Roger Donaldson, who gives us such terrors as the "artistic" blending of black and white and a digitally constructed White House exterior. And, spending two-and-a-half hours exploring as few facets of this story as possible, Roger Donaldson tries to keep us guessing.
There really isn't much that I can tell you about the events within Thirteen Days that you can't read in books, but in case you never attended junior high and think the Cuban Missile Crisis was a bad porno, here's the story: In 1962, the Soviets began putting nukes in Cuba, hoping to blow us away. Forget the fact that we had missiles in Europe and had similar attack capabilities -- the Soviets could have blown us away in about five minutes, and, as Americans, we were really pissed off about this.
Admittedly, the Cuban Missile Crisis was a bit before my time, but come on, do we have to see the movie? And even if we have to see the movie, does it have to be this bad? Every time a new character is introduced, they come complete with a subtitle bearing their name and position, and are then greeted. It's surprising Bruce Greenwood doesn't wear a nametag that reads, "Hello, My name is Mr. President."
Dramatic family montages, cheap stock footage, cliched characters, they're all here.  Imagine Apollo 13 if it were made really badly -- bad filmmaking coupled with an ending that you can't change (though Donaldson actually tries to trick us at many points by interspersing stock footage of nuclear explosions into the movie, we know better). The result is not a reliving of the Cuban Missile Crisis: It's a sickening exploitation of a historical event. Don't believe me? Go to the movie's web site (see below) and check out the strategic military exercise, a game in which it's your patriotic responsibility to destroy all Russian forces.

The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews