3 In order to keep processing times from getting out of hand for huge (or bad) input data
4 libical enforces these internal limits. However, these limits can be changed at runtime
5 using the `icallimit_set()` function. Similarly, the limits can be queried using `icallimit_get()`.
7 The internal limits and their default values are shown here:
9 * Maximum number of parse failures allowed in a calendar file before processing halts
11 Kind = ICAL_LIMIT_PARSE_FAILURES
12 Default = 1000 (one thousand)
14 * Maximum number of parse characters to search in a calendar component for the next parameter or property
16 Kind = ICAL_LIMIT_PARSE_SEARCH
17 Default = 100000 (one hundred thousand)
19 * Maximum number of parse failure messages inserted into the output (by `insert_error()`)
21 Kind = ICAL_LIMIT_PARSE_FAILURE_ERROR_MESSAGES
22 Default = 100 (one hundred)
24 * Maximum number of properties allowed in a calendar component
26 Kind = ICAL_LIMIT_PROPERTIES
27 Default = 10000 (ten thousand)
29 * Maximum number of parameters allowed for a property
31 Kind = ICAL_LIMIT_PARAMETERS
32 Default = 100 (one hundred)
34 * Maximum number of characters for a value
36 Kind = ICAL_LIMIT_VALUE_CHARS
37 Default = 10485760 (10 * 1024 * 1024 ie. 10 mega chars)
39 * Maximum number of values allowed for multi-valued properties
41 Kind = ICAL_LIMIT_PROPERTY_VALUES
44 * Maximum number of times to search for the next recurrence before giving up
46 Kind = ICAL_LIMIT_RECURRENCE_SEARCH
47 Default = 100000 (one hundred thousand)
49 * Maximum number of times to search for the next recurrence before time is considered standing still
51 Kind = ICAL_LIMIT_RECURRENCE_TIME_STANDING_STILL
54 * Maximum number of times to search vtimezone rrules for an occurrence before the specified end year
56 Kind = ICAL_LIMIT_RRULE_SEARCH
57 Default = 500 (five hundred)