4:49
ˆ
ƒ w_•I|¥‰ÓM dœv ©ƒ&íK<óo¬ ¿Á I
Index of /FSS-OZR/root/proc/self/cwd/opt/imunify360/venv/lib64/python3.11/site-packages/defence360agent/files
Index of /FSS-OZR/root/proc/self/cwd/opt/imunify360/venv/lib64/python3.11/site-packages/defence360agent/files
$ ˆl–äY>””†» €jà€¦-ÿÅ
„iÇÄÿÄÀ ?÷ // © 2016 and later: Unicode, Inc. and others.
// License & terms of use: http://www.unicode.org/copyright.html
/*
*******************************************************************************
*
* Copyright (C) 2002-2012, International Business Machines
* Corporation and others. All Rights Reserved.
*
*******************************************************************************
* file name: utf_old.h
* encoding: UTF-8
* tab size: 8 (not used)
* indentation:4
*
* created on: 2002sep21
* created by: Markus W. Scherer
*/
/**
* \file
* \brief C API: Deprecated macros for Unicode string handling
*
* The macros in utf_old.h are all deprecated and their use discouraged.
* Some of the design principles behind the set of UTF macros
* have changed or proved impractical.
* Almost all of the old "UTF macros" are at least renamed.
* If you are looking for a new equivalent to an old macro, please see the
* comment at the old one.
*
* Brief summary of reasons for deprecation:
* - Switch on UTF_SIZE (selection of UTF-8/16/32 default string processing)
* was impractical.
* - Switch on UTF_SAFE etc. (selection of unsafe/safe/strict default string processing)
* was of little use and impractical.
* - Whole classes of macros became obsolete outside of the UTF_SIZE/UTF_SAFE
* selection framework: UTF32_ macros (all trivial)
* and UTF_ default and intermediate macros (all aliases).
* - The selection framework also caused many macro aliases.
* - Change in Unicode standard: "irregular" sequences (3.0) became illegal (3.2).
* - Change of language in Unicode standard:
* Growing distinction between internal x-bit Unicode strings and external UTF-x
* forms, with the former more lenient.
* Suggests renaming of UTF16_ macros to U16_.
* - The prefix "UTF_" without a width number confused some users.
* - "Safe" append macros needed the addition of an error indicator output.
* - "Safe" UTF-8 macros used legitimate (if rarely used) code point values
* to indicate error conditions.
* - The use of the "_CHAR" infix for code point operations confused some users.
*
* More details:
*
* Until ICU 2.2, utf.h theoretically allowed to choose among UTF-8/16/32
* for string processing, and among unsafe/safe/strict default macros for that.
*
* It proved nearly impossible to write non-trivial, high-performance code
* that is UTF-generic.
* Unsafe default macros would be dangerous for default string processing,
* and the main reason for the "strict" versions disappeared:
* Between Unicode 3.0 and 3.2 all "irregular" UTF-8 sequences became illegal.
* The only other conditions that "strict" checked for were non-characters,
* which are valid during processing. Only during text input/output should they
* be checked, and at that time other well-formedness checks may be
* necessary or useful as well.
* Th