SYNOPSIS
        #include <rtlimits.h>

        int * query_limits()
        int * query_limits(int default)

DESCRIPTION
        Return an array with the current runtime limits, resp. if <defaults>
        is true, the default runtime limits. The entries in the returned
        array are:

          int[LIMIT_EVAL]:    the max number of eval costs
          int[LIMIT_ARRAY]:   the max number of array entries
          int[LIMIT_MAPPING_SIZE]: the max number of mapping values
          int[LIMIT_MAPPING_KEYS]: the max number of mapping entries
             (LIMIT_MAPPING is an alias for LIMIT_MAPPING_KEYS)
          int[LIMIT_BYTE]:    the max number of bytes handled with
                                one read_bytes()/write_bytes() call.
          int[LIMIT_FILE]:    the max number of bytes handled with
                                one read_file()/write_file() call.
          int[LIMIT_CALLOUTS]: the number of callouts at one time.
          int[LIMIT_COST]:    how to account the current cost.
          int[LIMIT_MEMROY]:  the max. number of bytes which can be 
                              _additionally_ allocated/used 
                              _per top-level execution thread_

        For all limits except LIMIT_COST a limit of '0' aka LIMIT_UNLIMITED
        means 'no limit'.

        The value for LIMIT_COST has these meanings:

          value > 0: the execution will cost minimum(<value>, actual cost) .

          value = 0: if the current LIMIT_EVAL is larger than the calling
                     LIMIT_EVAL, the evaluation will cost only 10; otherwise
                     the full cost will be accounted.

          value < 0: (-value)% of the current evaluation cost will be
                     accounted; -100 obviously means 'full cost'.

EXAMPLES
        query_limits()
          --> returns the current runtime limits

        query_limits(1)
          --> returns the default runtime limits

HISTORY
        Introduced in LDMud 3.2.7.
        LIMIT_CALLOUTS introduced in LDMud 3.2.9.
        LIMIT_COST introduced in LDMud 3.3.563.
        LDMud 3.3.677 introduced LIMIT_MAPPING_KEYS, LIMIT_MAPPING_SIZE.
        LDMud 3.5.0 introduced LIMIT_MEMORY.

SEE ALSO
        limited(E), set_limits(E)