# php_manual

id: OAuthProvider::callconsumerHandler
type: function
doc:
<comment>Description:</comment>
  Calls the consumerNonceHandler callback
  
  Calls the registered consumer handler callback function, which is set with
  OAuthProvider::consumerHandler.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::consumerHandler


id: OAuthProvider::calltokenHandler
type: function
doc:
<comment>Description:</comment>
  Calls the tokenNonceHandler callback
  
  Calls the registered token handler callback function, which is set with
  OAuthProvider::tokenHandler.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::tokenHandler


id: OAuthProvider::checkOAuthRequest
type: function
doc:
<comment>Description:</comment>
  Check an oauth request
  
  Checks an OAuth request.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string</info>  <strong>$uri</strong>     The optional URI, or endpoint.
  <info>string</info>  <strong>$method</strong>  The HTTP method. Optionally pass in one of the  <info>OAUTH_HTTP_METHOD_*</info> OAuth
                   constants.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::reportProblem


id: OAuthProvider::consumerHandler
type: function
doc:
<comment>Description:</comment>
  Set the consumerHandler handler callback
  
  Sets the consumer handler callback, which will later be called with
  OAuthProvider::callConsumerHandler.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::callConsumerHandler


id: OAuthProvider::generateToken
type: function
doc:
<comment>Description:</comment>
  Generate a random token
  
  Generates a <info>string</info> of pseudo-random bytes.

<comment>Param:</comment>
  <info>int</info>   <strong>$size</strong>    The desired token length, in terms of bytes.
  <info>bool</info>  <strong>$strong</strong>  Setting to <info>true</info> means <return>/dev/random</return> will be used for entropy, as otherwise the
                 non-blocking <return>/dev/urandom</return> is used. This parameter is ignored on Windows.

<comment>Return:</comment>
  <info>string</info>  The generated token, as a <info>string</info> of bytes.

<comment>See Also:</comment>
   * <strong>openssl_random_pseudo_bytes()</strong>
   * <strong>mcrypt_create_iv()</strong>


id: OAuthProvider::is2LeggedEndpoint
type: function
doc:
<comment>Description:</comment>
  is2LeggedEndpoint
  
  The 2-legged flow, or request signing. It does not require a token.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$params_array</strong>  

<comment>Return:</comment>
  <info>void</info>  An <class>OAuthProvider</class> <info>object</info>.

<comment>See Also:</comment>
   * OAuthProvider::__construct


id: OAuthProvider::isRequestTokenEndpoint
type: function
doc:
<comment>Description:</comment>
  Sets isRequestTokenEndpoint
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>bool</info>  <strong>$will_issue_request_token</strong>  Sets whether or not it will issue a request token, thus
                                   determining if OAuthProvider::tokenHandler needs to be called.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::setRequestTokenPath
   * OAuthProvider::reportProblem


id: OAuthProvider::removeRequiredParameter
type: function
doc:
<comment>Description:</comment>
  Remove a required parameter
  
  Removes a required parameter.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string</info>  <strong>$req_params</strong>  The required parameter to be removed.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * OAuthProvider::setParam
   * OAuthProvider::addRequiredParameter


id: OAuthProvider::reportProblem
type: function
doc:
<comment>Description:</comment>
  Report a problem
  
  Pass in a problem as an <class>OAuthException</class>, with possible problems listed in the OAuth constants
  section.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string</info>  <strong>$oauthexception</strong>  The <class>OAuthException</class>.

<comment>Return:</comment>
  <info>string</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::checkOAuthRequest
   * OAuthProvider::isRequestTokenEndpoint


id: OAuthProvider::setParam
type: function
doc:
<comment>Description:</comment>
  Set a parameter
  
  Sets a parameter.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string</info>  <strong>$param_key</strong>  The parameter key.
  <info>mixed</info>   <strong>$param_val</strong>  The optional parameter value.
                      
                      To exclude a parameter from signature verification, set its value to <info>null</info>.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * OAuthProvider::addRequiredParameter


id: OAuthProvider::setRequestTokenPath
type: function
doc:
<comment>Description:</comment>
  Set request token path
  
  Sets the request tokens path.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string</info>  <strong>$path</strong>  The path.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuthProvider::tokenHandler


id: OAuthProvider::timestampNonceHandler
type: function
doc:
<comment>Description:</comment>
  Set the timestampNonceHandler handler callback
  
  Sets the timestamp nonce handler callback, which will later be called with
  OAuthProvider::callTimestampNonceHandler. Errors related to timestamp/nonce are thrown to this
  callback.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::callTimestampNonceHandler


id: OAuthProvider::tokenHandler
type: function
doc:
<comment>Description:</comment>
  Set the tokenHandler handler callback
  
  Sets the token handler callback, which will later be called with OAuthProvider::callTokenHandler.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * OAuthProvider::callTokenHandler


id: OCICollection
type: class
doc:
<comment>Description:</comment>
  OCI8 Collection functionality.
  
  The <class>OCI-Collection</class> class was renamed to <class>OCICollection</class> in PHP 8 OCI8 3.0.0 to align with PHP naming
  standards.


id: OCICollection::append
type: function
doc:
<comment>Description:</comment>
  Appends element to the collection
  
  Appends element to the end of the collection.

<comment>Param:</comment>
  <info>string</info>  <strong>$value</strong>  The value to be added to the collection.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCICollection::assign
type: function
doc:
<comment>Description:</comment>
  Assigns a value to the collection from another existing collection
  
  Assigns a value to the collection from another, previously created collection. Both collections
  must be created with  <strong>oci_new_collection()</strong> prior to using them.

<comment>Param:</comment>
  <info>OCICollection</info>  <strong>$from</strong>  An instance of OCICollection.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCICollection::assignElem
type: function
doc:
<comment>Description:</comment>
  Assigns a value to the element of the collection
  
  Assigns a value to the element with index <strong>$index</strong>.

<comment>Param:</comment>
  <info>int</info>     <strong>$index</strong>  The element index. First index is 0.
  <info>string</info>  <strong>$value</strong>  Can be a string or a number.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCICollection::free
type: function
doc:
<comment>Description:</comment>
  Frees the resources associated with the collection object
  
  Frees the resources associated with the collection object.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCICollection::getElem
type: function
doc:
<comment>Description:</comment>
  Returns value of the element
  
  Returns element's value with the index <strong>$index</strong> (0-based).

<comment>Param:</comment>
  <info>int</info>  <strong>$index</strong>  The element index. First index is 0.

<comment>Return:</comment>
  <info>string|float|null|false</info>  Returns <info>false</info> if such element doesn't exist; <info>null</info> if element is <info>null</info>;
                           string if element is column of a string datatype or number if element is
                           numeric field.

<comment>See Also:</comment>
   * 


id: OCICollection::max
type: function
doc:
<comment>Description:</comment>
  Returns the maximum number of elements in the collection
  
  Returns the maximum number of elements in the collection.

<comment>Return:</comment>
  <info>int|false</info>  Returns the maximum number as an integer, or <info>false</info> on errors.
             
             If the returned value is 0, then the number of elements is not limited.

<comment>See Also:</comment>
   * 


id: OCICollection::size
type: function
doc:
<comment>Description:</comment>
  Returns size of the collection
  
  Returns the size of the collection.

<comment>Return:</comment>
  <info>int|false</info>  Returns the number of elements in the collection or <info>false</info> on error.

<comment>See Also:</comment>
   * 


id: OCICollection::trim
type: function
doc:
<comment>Description:</comment>
  Trims elements from the end of the collection
  
  Trims <strong>$num</strong> of elements from the end of the collection.

<comment>Param:</comment>
  <info>int</info>  <strong>$num</strong>  The number of elements to be trimmed.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob
type: class
doc:
<comment>Description:</comment>
  OCI8 LOB functionality for large binary (BLOB) and character (CLOB) objects.
  
  The <class>OCI-Lob</class> class was renamed to <class>OCILob</class> in PHP 8 and PECL OCI8 3.0.0 to align with PHP naming
  standards.


id: OCILob::append
type: function
doc:
<comment>Description:</comment>
  Appends data from the large object to another large object
  
  Appends data from the large object to the end of another large object.
  
  Writing to the large object with this method will fail if buffering was previously enabled. You
  must disable buffering before appending. You may need to flush buffers with  before disabling
  buffering.

<comment>Param:</comment>
  <info>OCILob</info>  <strong>$from</strong>  The copied LOB.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 
   * 


id: OCILob::close
type: function
doc:
<comment>Description:</comment>
  Closes LOB descriptor
  
  Closes descriptor of LOB or FILE. This function should be used only with .

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob::eof
type: function
doc:
<comment>Description:</comment>
  Tests for end-of-file on a large object's descriptor
  
  Tells whether the internal pointer of large object is at the end of LOB.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if internal pointer of large object is at the end of LOB. Otherwise returns
        <info>false</info>.

<comment>See Also:</comment>
   * 


id: OCILob::erase
type: function
doc:
<comment>Description:</comment>
  Erases a specified portion of the internal LOB data
  
  Erases a specified portion of the internal LOB data starting at a specified <strong>$offset</strong>. If called
  without parameters, it erases all LOB data.
  
  For BLOBs, erasing means that the existing LOB value is overwritten with zero-bytes. For CLOBs,
  the existing LOB value is overwritten with spaces.

<comment>Param:</comment>
  <info>int|null</info>  <strong>$offset</strong>  
  <info>int|null</info>  <strong>$length</strong>  

<comment>Return:</comment>
  <info>int|false</info>  Returns the actual number of characters/bytes erased  başarısızlık durumunda <info>false</info>
             döner.

<comment>See Also:</comment>
   * 


id: OCILob::export
type: function
doc:
<comment>Description:</comment>
  Exports LOB's contents to a file
  
  Exports LOB contents to a file.

<comment>Param:</comment>
  <info>string</info>    <strong>$filename</strong>  Path to the file.
  <info>int|null</info>  <strong>$offset</strong>    Indicates from where to start exporting.
  <info>int|null</info>  <strong>$length</strong>    Indicates the length of data to be exported.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob::flush
type: function
doc:
<comment>Description:</comment>
  Flushes/writes buffer of the LOB to the server
  
  <strong>OCILob::flush()</strong> actually writes data to the server.

<comment>Param:</comment>
  <info>int</info>  <strong>$flag</strong>  By default, resources are not freed, but using flag  <info>OCI_LOB_BUFFER_FREE</info> you can do it
              explicitly. Be sure you know what you're doing - next read/write operation to the same
              part of LOB will involve a round-trip to the server and initialize new buffer
              resources. It is recommended to use  <info>OCI_LOB_BUFFER_FREE</info> flag only when you are not
              going to work with the LOB anymore.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.
        
        Returns <info>false</info> if buffering was not enabled or an error occurred.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::free
type: function
doc:
<comment>Description:</comment>
  Frees resources associated with the LOB descriptor
  
  Frees resources associated with the descriptor, previously allocated with  <strong>oci_new_descriptor()</strong>.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: OCILob::getBuffering
type: function
doc:
<comment>Description:</comment>
  Returns current state of buffering for the large object
  
  Tells whether the buffering for the large object is on or off.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>false</info> if buffering for the large object is off and <info>true</info> if buffering is used.

<comment>See Also:</comment>
   * 


id: OCILob::import
type: function
doc:
<comment>Description:</comment>
  Imports file data to the LOB
  
  Writes data from the <strong>$filename</strong> in to the current position of large object.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  Path to the file.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::load
type: function
doc:
<comment>Description:</comment>
  Returns large object's contents
  
  Returns large object's contents. As script execution is terminated when the memory_limit is
  reached, ensure that the LOB does not exceed this limit. In most cases it's recommended to use
  instead.

<comment>Return:</comment>
  <info>string|false</info>  Returns the contents of the object, or <info>false</info> on errors.

<comment>See Also:</comment>
   * 


id: OCILob::read
type: function
doc:
<comment>Description:</comment>
  Reads part of the large object
  
  Reads <strong>$length</strong> of bytes (BLOB) or characters (CLOB) from the current position of LOB's internal
  pointer.
  
  Reading stops when <strong>$length</strong> of bytes have been read for a BLOB, when <strong>$length</strong> of characters have
  been read for a CLOB, or when the end of the large object is reached. Internal pointer of the
  large object will be shifted on the amount of bytes/characters read.

<comment>Param:</comment>
  <info>int</info>  <strong>$length</strong>  The length of data to read, in bytes (BLOB) or characters (CLOB). Large values will
                be rounded down to 1 MB.

<comment>Return:</comment>
  <info>string|false</info>  Returns the contents as a string,  başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::rewind
type: function
doc:
<comment>Description:</comment>
  Moves the internal pointer to the beginning of the large object
  
  Sets the internal pointer to the beginning of the large object.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::save
type: function
doc:
<comment>Description:</comment>
  Saves data to the large object
  
  Saves <strong>$data</strong> to the large object.

<comment>Param:</comment>
  <info>string</info>  <strong>$data</strong>    The data to be saved.
  <info>int</info>     <strong>$offset</strong>  Can be used to indicate offset from the beginning of the large object.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::saveFile
type: function
doc:
<comment>Description:</comment>
  Takma Adı: OCILob::import
  
  Bu işlev şu işlevin takma adıdır:   <strong>OCILob::import()</strong>.


id: OCILob::seek
type: function
doc:
<comment>Description:</comment>
  Sets the internal pointer of the large object
  
  Sets the internal pointer of the large object.

<comment>Param:</comment>
  <info>int</info>  <strong>$offset</strong>  Indicates the amount of bytes, on which internal pointer should be moved from the
                position, pointed by <strong>$whence</strong>.
  <info>int</info>  <strong>$whence</strong>  May be one of: <info>OCI_SEEK_SET</info> - sets the position equal to  <strong>$offset</strong> <info>OCI_SEEK_CUR</info> -
                adds <strong>$offset</strong>  bytes to the current position   <info>OCI_SEEK_END</info> - adds <strong>$offset</strong> bytes to
                the end of large object (use negative value to move to a position before the end of
                large object)

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * 
   * 


id: OCILob::setBuffering
type: function
doc:
<comment>Description:</comment>
  Changes current state of buffering for the large object
  
  Sets the buffering for the large object, depending on the value of the <strong>$mode</strong> parameter.
  
  Use of this function may provide performance improvements by buffering small reads and writes of
  LOBs by reducing the number of network round-trips and LOB versions.  <strong>OCILob::flush()</strong> should be
  used to flush buffers, when you have finished working with the large object.

<comment>Param:</comment>
  <info>bool</info>  <strong>$mode</strong>  <info>true</info> for on and <info>false</info> for off.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner. Repeated calls to this method
        with the same flag will return <info>true</info>.

<comment>See Also:</comment>
   * 


id: OCILob::size
type: function
doc:
<comment>Description:</comment>
  Returns size of large object
  
  Gets the size of the large object.

<comment>Return:</comment>
  <info>int|false</info>  Returns length of large object value  başarısızlık durumunda <info>false</info> döner. Empty objects
             have zero length.


id: OCILob::tell
type: function
doc:
<comment>Description:</comment>
  Returns the current position of internal pointer of large object
  
  Gets the current position of a LOB's internal pointer.

<comment>Return:</comment>
  <info>int|false</info>  Returns current position of a LOB's internal pointer or <info>false</info> if an error occurred.

<comment>See Also:</comment>
   * 
   * 
   * 


id: OCILob::truncate
type: function
doc:
<comment>Description:</comment>
  Truncates large object
  
  Truncates the LOB.

<comment>Param:</comment>
  <info>int</info>  <strong>$length</strong>  If provided, this method will truncate the LOB to <strong>$length</strong> bytes. Otherwise, it will
                completely purge the LOB.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob::write
type: function
doc:
<comment>Description:</comment>
  Writes data to the large object
  
  Writes data from the parameter <strong>$data</strong> into the current position of LOB's internal pointer.

<comment>Param:</comment>
  <info>string</info>    <strong>$data</strong>    The data to write in the LOB.
  <info>int|null</info>  <strong>$length</strong>  If this parameter is an integer, writing will stop after <strong>$length</strong> bytes have
                     been written or the end of <strong>$data</strong> is reached, whichever comes first.

<comment>Return:</comment>
  <info>int|false</info>  Returns the number of bytes written  başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob::writeTemporary
type: function
doc:
<comment>Description:</comment>
  Writes a temporary large object
  
  Creates a temporary large object and writes <strong>$data</strong> to it.
  
  You should use  when you are done with this object.

<comment>Param:</comment>
  <info>string</info>  <strong>$data</strong>  The data to write.
  <info>int</info>     <strong>$type</strong>  Can be one of the following: <info>OCI_TEMP_BLOB</info> is used to create temporary BLOBs
                 <info>OCI_TEMP_CLOB</info> is used to create temporary CLOBs

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 


id: OCILob::writeToFile
type: function
doc:
<comment>Description:</comment>
  Takma Adı: OCILob::export
  
  Bu işlev şu işlevin takma adıdır:  <strong>OCILob::export()</strong>.


id: OCI_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_fetch_all()</strong> and <strong>oci_fetch_array()</strong> to get results as an associative array.


id: OCI_BOTH
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_fetch_all()</strong> and <strong>oci_fetch_array()</strong> to get results as an array with both associative
  and number indices.


id: OCI_B_BFILE
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding BFILEs.


id: OCI_B_BIN
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> to bind RAW values.


id: OCI_B_BLOB
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding BLOBs.


id: OCI_B_BOL
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> to bind a PL/SQL BOOLEAN variable.


id: OCI_B_CFILEE
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding CFILEs.


id: OCI_B_CLOB
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding CLOBs.


id: OCI_B_CURSOR
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding cursors, previously allocated with <strong>oci_new_descriptor()</strong>.


id: OCI_B_INT
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_array_by_name()</strong> to bind arrays of INTEGER.


id: OCI_B_NTY
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding named data types.


id: OCI_B_NUM
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_array_by_name()</strong> to bind arrays of NUMBER.


id: OCI_B_ROWID
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_bind_by_name()</strong> when binding ROWIDs.


id: OCI_COMMIT_ON_SUCCESS
type: constant
doc:
<comment>Description:</comment>
  Statement execution mode for <strong>oci_execute()</strong> call. Automatically commit changes when the statement
  has succeeded.


id: OCI_CRED_EXT
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_connect()</strong> for using Oracles' External or OS authentication.


id: OCI_DESCRIBE_ONLY
type: constant
doc:
<comment>Description:</comment>
  Statement execution mode for <strong>oci_execute()</strong>.  Use this mode if you want meta data such as the
  column names but don't want to fetch rows from the query.


id: OCI_DTYPE_FILE
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>oci_new_descriptor()</strong> to initialize a new FILE descriptor.


id: OCI_DTYPE_LOB
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>oci_new_descriptor()</strong> to initialize a new LOB descriptor.


id: OCI_DTYPE_ROWID
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>oci_new_descriptor()</strong> to initialize a new ROWID descriptor.


id: OCI_EXACT_FETCH
type: constant
doc:
<comment>Description:</comment>
  Obsolete. Statement fetch mode. Used when the application knows in advance exactly how many rows
  it will be fetching. This mode turns prefetching off for Oracle release 8 or later mode. The
  cursor is canceled after the desired rows are fetched which may result in reduced server-side
  resource usage.


id: OCI_NO_AUTO_COMMIT
type: constant
doc:
<comment>Description:</comment>
  Statement execution mode for <strong>oci_execute()</strong>. The transaction is not automatically committed when
  using this mode.  For readability in new code, use this value instead of the older, equivalent
  <info>OCI_DEFAULT</info> constant.


id: OCI_NUM
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_fetch_all()</strong> and <strong>oci_fetch_array()</strong> to get results as an enumerated array.


id: OCI_RETURN_LOBS
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_fetch_array()</strong> to get the data value of the LOB instead of the descriptor.


id: OCI_RETURN_NULLS
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_fetch_array()</strong> to get empty array elements if the row items value is <info>null</info>.


id: OCI_SYSDBA
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_connect()</strong> to connect with the SYSDBA privilege. The php.ini setting
  oci8.privileged_connect should be enabled to use this.


id: OCI_SYSOPER
type: constant
doc:
<comment>Description:</comment>
  Used with <strong>oci_connect()</strong> to connect with the SYSOPER privilege. The php.ini setting
  oci8.privileged_connect should be enabled to use this.


id: OPENSSL_ALGO_MD2
type: constant
doc:
<comment>Description:</comment>
  Bu sabit sadece PHP, MD2 desteğiyle derlenmişse kullanılabilir. OpenSSL 1.0.0+ derlenirken
  enable-md2 ve PHP derlenirken CFLAG olarak -DHAVE_OPENSSL_MD2_H aktarılmasını gerektirir.


id: OPENSSL_ALGO_SHA1
type: constant
doc:
<comment>Description:</comment>
  <strong>openssl_sign()</strong> ve <strong>openssl_verify()</strong> tarafından öntanımlı algoritma olarak kullanılır.


id: OPENSSL_CMS_BINARY
type: constant
doc:
<comment>Description:</comment>
  Normalde girdi iletisi, CMS belirtiminin gerektirdiği şekilde satır sonu olarak <return>CR</return> ve <return>LF</return>'i etkin
  bir şekilde kullanan "meşru" biçeme dönüştürülür. Bu seçenek mevcut olduğunda, herhangi bir
  dönüşüm yapılmaz. Bu, CMS biçeminde olmayabilecek ikil veriyi işlerken kullanışlıdır.


id: OPENSSL_CMS_DETACHED
type: constant
doc:
<comment>Description:</comment>
  Bir ileti imzalanırken, <return>"multipart/signed"</return> S/MIME türü ile açık metin imzalama kullanılır.
  <strong>openssl_cms_sign()</strong> işlevine <strong>$seçenekler</strong> ile herhangi bir seçenek belirtilmezse öntanımlı olarak bu
  yapılır. Bu seçeneği kapatırsanız, ileti mat imzalama kullanılarak imzalanır; ileti, eposta
  sunucularından aktarılırken dönüşüme daha dirençli olur fakat S/MIME'yi desteklemeyen posta
  istemcileri tarafından okunamaz.


id: OPENSSL_CMS_NOATTR
type: constant
doc:
<comment>Description:</comment>
  Normalde bir ileti imzalandığında, imzalama zamanını ve desteklenen simetrik algoritmaları içeren
  bir dizi öznitelik iletiye dahil edilir. Bu seçenekle dahil edilmez.


id: OPENSSL_CMS_NOCERTS
type: constant
doc:
<comment>Description:</comment>
  Bir iletiyi imzalarken normalde imzalayanın sertifikası iletiye dahil edilir - bu seçenekle hariç
  tutulur. Bu, imzalanan iletinin boyutunu azaltır, ancak doğrulayıcının imzalayanlar sertifikasının
  bir kopyasını yerel olarak bulundurması gerekir (örneğin, sertifika <strong>openssl_cms_verify()</strong> işlevine
  <strong>$güvenilmeyen_sertifikalar_dosyası</strong> ile aktarılarak kullanılabilir).


id: OPENSSL_CMS_NOINTERN
type: constant
doc:
<comment>Description:</comment>
  Bir ileti doğrulanırken, iletinin içerdiği sertifikalarda (varsa) normalde imza sertifikası
  aranır. Bu seçenek ile sadece <strong>openssl_cms_verify()</strong> işlevinin <strong>$güvenilmeyen_sertifikalar_dosyası</strong>
  bağımsız değişkeninde belirtilen sertifikalar kullanılır. Sağlanan sertifikalar yine de
  güvenilmeyen sertifikalar olarak kullanılabilir.


id: OPENSSL_CMS_NOVERIFY
type: constant
doc:
<comment>Description:</comment>
  İmzalı bir iletinin imzalayanlar sertifikasını doğrulanmaz. message.


id: OPENSSL_CMS_OLDMIMETYPE
type: constant
doc:
<comment>Description:</comment>
  PHP 8.3.0 ve sonrasında kullanılabilir. Bir iletiyi şifrelemek için içerik türü
  <return>application/x-pkcs7-mime</return> yerine <return>application/pkcs7-mime</return> yapılır.


id: OPENSSL_CMS_TEXT
type: constant
doc:
<comment>Description:</comment>
  Şifrelenmiş/imzalanmış iletiye <return>text/plain</return> içerik türü başlıklarını ekler. Şifre çözme veya
  doğrulama durumunda, bu başlıkları çıktıdan çıkarır - şifresi çözülen veya doğrulanan iletinin
  MIME türü <return>text/plain</return> değilse bir hata oluşur.


id: OPENSSL_ENCODING_DER
type: constant
doc:
<comment>Description:</comment>
  Kodlamanın DER olduğunu belirtir. (DER: Distinguished Encoding Rules - Seçkin Kodlama Kuralları).


id: OPENSSL_ENCODING_PEM
type: constant
doc:
<comment>Description:</comment>
  Kodlamanın PEM olduğunu belirtir. (PEM: Privacy-Enhanced Mail - Gizliliği Gelişkin Posta).


id: OPENSSL_KEYTYPE_EC
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek sadece PHP, OpenSSL 0.9.8+ ile derlendiği takdirde kullanılabilir.


id: OPENSSL_RAW_DATA
type: constant
doc:
<comment>Description:</comment>
  <strong>openssl_encrypt()</strong> veya <strong>openssl_decrypt()</strong> işlevine <info>OPENSSL_RAW_DATA</info> aktarılmışsa, veri olduğu gibi
  döndürülür. Belirtilmezse Base64 kodlu veri döndürülür.


id: OPENSSL_ZERO_PADDING
type: constant
doc:
<comment>Description:</comment>
  Öntanımlı olarak şifreleme işlemleri, standart blok doldurma kullanılarak doldurulur ve şifre
  çözülürken dolgu kontrol edilip kaldırılır. <strong>openssl_encrypt()</strong> veya <strong>openssl_decrypt()</strong> işlevine
  <info>OPENSSL_ZERO_PADDING</info> aktarılırsa, herhangi bir dolgu yapılmaz. Şifrelenen veya şifresi çözülen
  toplam veri miktarı blok boyutunun katları olmalıdır, aksi takdirde bir hata oluşur.


id: OP_ANONYMOUS
type: constant
doc:
<comment>Description:</comment>
  Haberler için bir .newsrc kullanmayın veya güncellemeyin (sadece NNTP için).


id: OP_HALFOPEN
type: constant
doc:
<comment>Description:</comment>
  IMAP ve NNTP isimleri için bir posta kutusu değil bir bağlantı açılır.


id: OpenSSLAsymmetricKey
type: class
doc:
<comment>Description:</comment>
  PHP 8.0.0 itibariyle, <return>OpenSSL Key</return> özkaynaklarının yerini alan tamamen kapalı sınıf.


id: OpenSSLCertificate
type: class
doc:
<comment>Description:</comment>
  PHP 8.0.0 itibariyle, <return>OpenSSL X.509</return> özkaynaklarının yerini alan tamamen kapalı sınıf.


id: OpenSSLCertificateSigningRequest
type: class
doc:
<comment>Description:</comment>
  PHP 8.0.0 itibariyle, <return>OpenSSL X.509 CSR</return> özkaynaklarının yerini alan tamamen kapalı sınıf.


id: OuterIterator
type: class
doc:
<comment>Description:</comment>
  Classes implementing <class>OuterIterator</class> can be used to iterate over iterators.


id: OuterIterator::getInnerIterator
type: function
doc:
<comment>Description:</comment>
  Returns the inner iterator for the current entry
  
  Returns the inner iterator for the current iterator entry.

<comment>Return:</comment>
  <info>Iterator|null</info>  Returns the inner iterator for the current entry if it exists, or <info>null</info> otherwise.


id: PASSWORD_ARGON2I
type: constant
doc:
<comment>Description:</comment>
  Argon2i algoritması ile yeni bir parola aşı üretmekte kullanılır.
  
  Desteklenen seçenekler:
  
  <return>memory_cost</return> (<info>int</info>) - Argon2 aşını hesaplamakta kullanılabilecek kilobibayt cinsinden azami bellek.
  <info>PASSWORD_ARGON2_DEFAULT_MEMORY_COST</info> öntanımlıdır.
  
  <return>time_cost</return> (<info>int</info>) - Argon2 aşını hesaplamak için gerekebilecek azami süre.
  <info>PASSWORD_ARGON2_DEFAULT_TIME_COST</info> öntanımlıdır.
  
  <return>threads</return> (<info>int</info>) - Argon2 aşını hesaplamak için kullanılacak evre sayısı.
  <info>PASSWORD_ARGON2_DEFAULT_THREADS</info> öntanımlıdır.
  
  PHP 7.2.0 ve sonrasında kullanılabilir.


id: PASSWORD_ARGON2ID
type: constant
doc:
<comment>Description:</comment>
  Argon2id algoritması ile yeni bir parola aşı üretmekte kullanılır. <info>PASSWORD_ARGON2I</info> için gereken
  seçenekler kullanılır.
  
  PHP 7.3.0 ve sonrasında kullanılabilir.


id: PASSWORD_ARGON2_DEFAULT_MEMORY_COST
type: constant
doc:
<comment>Description:</comment>
  Bir aş hesaplamaya çalışılırken kullanılacak bayt cinsinden öntanımlı bellek miktarı.
  
  PHP 7.2.0 ve sonrasında kullanılabilir.


id: PASSWORD_ARGON2_DEFAULT_THREADS
type: constant
doc:
<comment>Description:</comment>
  Argon2lib tarafından kullanılacak öntanımlı evre sayısı. libsodium eklentisi ile kullanılamaz.
  
  Available as of PHP 7.2.0.


id: PASSWORD_ARGON2_DEFAULT_TIME_COST
type: constant
doc:
<comment>Description:</comment>
  Bir aş hesaplamaya çalışılırken kullanılacak öntanımlı süre.
  
  PHP 7.2.0 ve sonrasında kullanılabilir.


id: PASSWORD_BCRYPT
type: constant
doc:
<comment>Description:</comment>
  <info>CRYPT_BLOWFISH</info> algoritması ile yeni bir parola aşı üretmekte kullanılır.
  
  Bu daima, "$2y$" <strong>crypt()</strong> biçemi kullanılan 60 karakterlik bir aş ile sonuçlanır.
  
  Desteklenen seçenekler:
  
  <return>salt</return> (<info>string</info>) - Parola aşlanırken kullanmak üzere elle bir tuz sağlamak için kullanılır. Bunun bir
  tuzun otomatik olarak oluşturulmasını geçersiz kılıp önleyeceği unutulmamalıdır.
  
  Belirtilmezse, aşlanan her parola için <strong>password_hash()</strong> tarafından rasgele bir tuz üretilir. Bu
  amaçlanan çalışma kipidir.
  
  PHP 7.0.0 ve sonrasında <return>salt</return> seçeneğinin kullanımı önerilmemektedir. Artık öntanımlı olarak
  üretilen tuzun kullanımı öneriliyor.
  
  <return>cost</return> (<info>int</info>) - Kullanılması gereken algoritmik maliyeti belirtir. Bu değerin örnekleri <strong>crypt()</strong>
  işlevinde bulunabilir.
  
  Belirtilmezse, <return>10</return> öntanımlı değeri kullanılır. Bu iyi bir temel maliyettir, ancak donanımınıza
  bağlı olarak arttırılabilir.


id: PASSWORD_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Bir algoritma sağlanmazsa aşlama için kullanılacak öntanımlı algoritma. Desteklenebilecek daha
  yeni ve daha güçlü algoritmalar çıktıkça PHP'nin yeni sürümlerinde öntanımlı algoritma
  değişebilir.
  
  Bu sabit, PHP'ye yeni ve daha güçlü algoritmalar eklendikçe zamanla değişmek üzere tasarlanmıştır.
  Bu sebeple, bu sabitin kullanımından kaynaklanan sonucun uzunluğu zamanla değişebilir. Bu
  bakımdan, sonucun 60 karakterden fazla genişleyebilen bir veritabanı sütununda saklanması önerilir
  (255 önerilen genişliktir).
  
  Bu sabit için değerler:
  
  PHP 5.5.0 - <info>PASSWORD_BCRYPT</info>


id: PDO
type: class
doc:
<comment>Description:</comment>
  PHP ile bir veritabanı sunucusu arasındaki bağlantıyı temsil eder.


id: PDO::ATTR_AUTOCOMMIT
type: constant
doc:
<comment>Description:</comment>
  <info>false</info> olduğu takdirde, PDO otomatik veri gönderimini iptal eder, böylece bağlantı bir veri
  hareketi (transaction) başlatır.


id: PDO::ATTR_CASE
type: constant
doc:
<comment>Description:</comment>
  Sütun isimlerindeki harflerin <return>PDO::CASE_*</return> sabitlerine göre belirtilmesini sağlar.


id: PDO::ATTR_CLIENT_VERSION
type: constant
doc:
<comment>Description:</comment>
  Bu salt okunur bir özelliktir. PDO sürücüsünün kullandığı istemci kütüphanesinin sürüm bilgisini
  döndürür.


id: PDO::ATTR_CURSOR
type: constant
doc:
<comment>Description:</comment>
  Gösterici türünü seçer. Desteklenen gösterici türleri: <info>PDO::CURSOR_FWDONLY</info> ve <info>PDO::CURSOR_SCROLL</info>.
  İhtiyacınızın kaydırılabilir bir gösterici olup olmadığına dair bir fikriniz yoksa seçiminizi
  <info>PDO::CURSOR_FWDONLY</info> sabitinden yana kullanın.


id: PDO::ATTR_CURSOR_NAME
type: constant
doc:
<comment>Description:</comment>
  Bir gösterici için kullanılacak ismi tanımlar veya döndürür. Kaydırılabilir göstericiler ve konum
  belirterek yapılan güncelemeler için çok kullanışlıdır.


id: PDO::ATTR_DEFAULT_STR_PARAM
type: constant
doc:
<comment>Description:</comment>
  Dizge bağımsız değişkenin öntanımlı türünü belirler. Değer olarak sadece <info>PDO::PARAM_STR_NATL</info> veya
  <info>PDO::PARAM_STR_CHAR</info> atanabilir.
  
  PHP 7.2.0'dan beri kullanılabilir..


id: PDO::ATTR_DRIVER_NAME
type: constant
doc:
<comment>Description:</comment>
  Sürücü ismini döndürür.
  
  - <info>PDO::ATTR_DRIVER_NAME</info> kullanımıgetAttribute(PDO::ATTR_DRIVER_NAME) == 'mysql') { echo "Burada
  mysql üzerinde mysql'e özgü bir şeyler yapılıyor\n";
  }
  ?>
  ]]>


id: PDO::ATTR_FETCH_CATALOG_NAMES
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesinde döndürülen her sütun isminin başına katalog ismini yerleştirir. Katalog ismi ile
  sütun ismi arasına bir nokta konur. Bu özellik sürücü seviyesinde desteklenir; kullandığınız
  sürücü bu özelliği desteklemeyebilir.


id: PDO::ATTR_FETCH_TABLE_NAMES
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesinde döndürülen her sütun isminin başına tablo ismini yerleştirir.Tablo ismi ile sütun
  ismi arasına bir nokta konur. Bu özellik sürücü seviyesinde desteklenir; kullandığınız sürücü bu
  özelliği desteklemeyebilir.


id: PDO::ATTR_PERSISTENT
type: constant
doc:
<comment>Description:</comment>
  Yeni bir bağlantı oluşturmak yerine kalıcı bir bağlantı ister. Ayrıntılı bilgi için  sayfasına
  bakınız.


id: PDO::ATTR_PREFETCH
type: constant
doc:
<comment>Description:</comment>
  Önalım boyutunun ayarlanması uygulamanızın bellek kullanım hızını dengeleyebilmenizi sağlar. Her
  veritabanı/sürücü önalım boyutunun ayarlanmasına izin vermez. Önalım boyutu ne kadar büyük
  seçilirse yüksek bellek kullanımı pahasına başarım o kadar artar.


id: PDO::ATTR_SERVER_INFO
type: constant
doc:
<comment>Description:</comment>
  Bu salt okunur bir özelliktir. PDO'nun bağlı olduğu veritabanı sunucusu hakkında bazı temel
  bilgileri döndürür.


id: PDO::ATTR_SERVER_VERSION
type: constant
doc:
<comment>Description:</comment>
  Bu salt okunur bir özelliktir. PDO'nun bağlı olduğu veritabanı sunucusunun sürüm bilgisini
  döndürür.


id: PDO::ATTR_STRINGIFY_FETCHES
type: constant
doc:
<comment>Description:</comment>
  Getirilen tüm değerlerin dizge olarak değerlendirilmesini sağlar.


id: PDO::CASE_NATURAL
type: constant
doc:
<comment>Description:</comment>
  Sütun isimleri veritabanı sürücüsünün döndürdüğü haliyle bırakılır.


id: PDO::CURSOR_FWDONLY
type: constant
doc:
<comment>Description:</comment>
  Sadece ileri yönde hareket eden bir göstericiye sahip bir <class>PDOStatement</class> nesnesi oluşturur. PHP'deki
  en hızlı ve en çok kullanılan veriye erişim yöntemi olarak bu gösterici öntanımlı göstericidir.


id: PDO::CURSOR_SCROLL
type: constant
doc:
<comment>Description:</comment>
  Kaydırılabilir göstericili bir <class>PDOStatement</class> nesnesi oluşturur. Satırların sonuç kümesinden nasıl
  döndürüleceğini belirtmek için <return>PDO::FETCH_ORI_*</return> sabitlerini kullanın.


id: PDO::ERRMODE_EXCEPTION
type: constant
doc:
<comment>Description:</comment>
  Bir hatanın oluşması bir <class>PDOException</class> istisnası ile sonuçlanır. Bu özellik ile ilgili ayrıntılı
  bilgi için  sayfasına bakınız.


id: PDO::ERRMODE_SILENT
type: constant
doc:
<comment>Description:</comment>
  Bir hata oluştuğunda bir istisna veya bir hata döndürülmez. Geliştiricinin hataları yakalayıp
  gereğini yapacağı varsayılır. Bu öntanımlı kiptir. Bu özellik ile ilgili ayrıntılı bilgi için
  sayfasına bakınız.


id: PDO::ERRMODE_WARNING
type: constant
doc:
<comment>Description:</comment>
  Bir hata oluştuğunda bir PHP <info>E_WARNING</info> iletisi çıktılanır. Bu özellik ile ilgili ayrıntılı bilgi
  için  sayfasına bakınız.


id: PDO::ERR_NONE
type: constant
doc:
<comment>Description:</comment>
  SQL deyiminin hatasız ve uyarısız başarıyla çalıştırıldığı anlamına gelen SQLSTATE '00000'
  karşılığıdır. Bir hata oluştuğunda hatayı PDO::errorCode veya PDOStatement::errorCode ile
  saptarken kolaylık olsun diye bu sabit vardır. Bunu normal olarak yöntemden dönen kodu inceleyerek
  saptayabilirsiniz.


id: PDO::FETCH_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırının, sütun isimleriyle indislenmiş bir dizi olarak
  döndürüleceğini belirtir. Eğer sonuç kümesi aynı isimde birden fazla sütun içeriyorsa her sütun
  için tek bir değer döner.


id: PDO::FETCH_BOTH
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırının, hem sütun isimleriyle hem de sütun numaralarıyla
  indislenmiş bir dizi olarak olarak döndürüleceğini belirtir. İlk sütunun indisi 0'dır.


id: PDO::FETCH_BOUND
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki sütun değerlerini PDOStatement::bindParam veya
  PDOStatement::bindColumn yönteminde SQL bağımsız değişkenleri ile ilişkilendirilip PHP
  değişkenlerine atanacağını ve <info>true</info> döndürüleceğini belirtir.


id: PDO::FETCH_CLASS
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sınıf özellikleri sütun isimleriyle eşlenerek elde edilen sınıfın yeni bir örneğini
  döndüreceğini belirtir.
  
  İstenen sınıf içinde özellik mevcut değilse sihirli __set yöntemi çağrılır.


id: PDO::FETCH_COLUMN
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki sonraki satırdan istenen tek bir sütunu döndüreceğini belirtir.


id: PDO::FETCH_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Kullanılacak öntanımlı fetch kipini belirtir. PHP 8.0.7 ve sonrasında kullanılabilir.


id: PDO::FETCH_FUNC
type: constant
doc:
<comment>Description:</comment>
  Verinin anında işlenmesi yoluyla tamamen özelleştirmeye izin verir (sadece PDOStatement::fetchAll
  içinde geçerlidir).


id: PDO::FETCH_GROUP
type: constant
doc:
<comment>Description:</comment>
  Grup değer olarak döner. Normal olarak <info>PDO::FETCH_COLUMN</info> veya <info>PDO::FETCH_KEY_PAIR</info> ile birlikte.


id: PDO::FETCH_INTO
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sınıf özellikleri sütun isimleriyle eşlenerek elde edilen sınıfın mevcut bir örneğini
  güncelleyeceğini belirtir.


id: PDO::FETCH_KEY_PAIR
type: constant
doc:
<comment>Description:</comment>
  İlk sütunun anahtar diğer sütunların ise birer değer olduğu bir dizi döner.


id: PDO::FETCH_LAZY
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırı, değişken isimlerinin sütun isimlerine karşılık geldiği bir
  nesne olarak döndüreceğini belirtir. <info>PDO::FETCH_LAZY</info> sütun isimlerine nesnenin değişkenleri olarak
  erişilebilmesini sağlar. PDOStatement::fetchAll içinde geçersizdir.


id: PDO::FETCH_NAMED
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırının, sütun isimleriyle indislenmiş bir dizi olarak olarak
  döndüreleceğini belirtir. Eğer sonuç kümesi aynı isimde birden fazla sütun içeriyorsa her sütun
  için bir değerler dizisi döner.


id: PDO::FETCH_NUM
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırının, sütun numaralarıyla indislenmiş bir dizi olarak olarak
  döndüreleceğini belirtir. İlk sütunun indisi 0'dır.


id: PDO::FETCH_OBJ
type: constant
doc:
<comment>Description:</comment>
  Yöntemin, sonuç kümesindeki her satırının, özellik isimlerinin sütun isimlerine karşılık geldiği
  bir nesne olarak döndüreceğini belirtir.


id: PDO::FETCH_ORI_ABS
type: constant
doc:
<comment>Description:</comment>
  İstenen satırı sonuç kümesindeki satır numarasına göre döndürür. Sadece kaydırılabilir
  göstericiler için geçerlidir.


id: PDO::FETCH_ORI_FIRST
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesindeki ilk satırı döndürür. Sadece kaydırılabilir göstericiler için geçerlidir.


id: PDO::FETCH_ORI_LAST
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesindeki son satırı döndürür. Sadece kaydırılabilir göstericiler için geçerlidir.


id: PDO::FETCH_ORI_NEXT
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesindeki sonraki satırı döndürür. Sadece kaydırılabilir göstericiler için geçerlidir.


id: PDO::FETCH_ORI_PRIOR
type: constant
doc:
<comment>Description:</comment>
  Sonuç kümesindeki önceki satırı döndürür. Sadece kaydırılabilir göstericiler için geçerlidir.


id: PDO::FETCH_ORI_REL
type: constant
doc:
<comment>Description:</comment>
  İstenen satırı, göstericinin sonuç kümesindeki konumuna göreli olarak döndürür. Sadece
  kaydırılabilir göstericiler için geçerlidir.


id: PDO::FETCH_SERIALIZE
type: constant
doc:
<comment>Description:</comment>
  Nesnenin dizgeleştirilmiş olarak döndürülmesi dışında <info>PDO::FETCH_INTO</info> gibidir. Bu seçenek etkinken
  sınıf kurucusu asla çağrılmamaktadır. PHP 8.1.0 ve sonrasında kullanımı önerilmiyor.


id: PDO::MYSQL_ATTR_FOUND_ROWS
type: constant
doc:
<comment>Description:</comment>
  Değişen satırların değil, bulunan (eşleşen) satırların satısı döner.


id: PDO::MYSQL_ATTR_IGNORE_SPACE
type: constant
doc:
<comment>Description:</comment>
  İşlev isimlerinden sonra boşluklara izin verir. Tüm işlev isimlerini ayrılmış sözcük haline
  getirir.


id: PDO::MYSQL_ATTR_INIT_COMMAND
type: constant
doc:
<comment>Description:</comment>
  MySQL sunucusuna bağlanırken çalıştırılacak komut. Yeniden bağlantı sırasında otomatik olarak bu
  komut çalıştırılır.
  
  Bu sabitin, yeni bir veritabanı tanıtıcısı oluştururken yalnızca <strong>$driver_options</strong> dizisinde
  kullanılabileceğini unutmayın.


id: PDO::MYSQL_ATTR_LOCAL_INFILE
type: constant
doc:
<comment>Description:</comment>
  <return>LOAD LOCAL INFILE</return> etkin olur.
  
  Bu sabitin, yeni bir veritabanı tanıtıcısı oluştururken yalnızca <strong>$driver_options</strong> dizisinde
  kullanılabileceğini unutmayın.


id: PDO::MYSQL_ATTR_LOCAL_INFILE_DIRECTORY
type: constant
doc:
<comment>Description:</comment>
  LOCAL DATA yüklemesinin bu belirlenmiş dizinde bulunan dosyalarla sınırlanmasına izin verir. PHP
  8.1.0 ve sonrasında kullanılabilir.
  
  Bu sabitin, yeni bir veritabanı tanıtıcısı oluştururken yalnızca <strong>$driver_options</strong> dizisinde
  kullanılabileceğini unutmayın.


id: PDO::MYSQL_ATTR_MAX_BUFFER_SIZE
type: constant
doc:
<comment>Description:</comment>
  Azami tampon büyüklüğü; 1 MiB öntanımlıdır. Derleme mysqlnd'ye rağmen yapıldığında bu sabit
  desteklenmez.


id: PDO::MYSQL_ATTR_MULTI_STATEMENTS
type: constant
doc:
<comment>Description:</comment>
  <info>false</info> olarak ayarlandığında hem <strong>PDO::prepare()</strong> hem de <strong>PDO::query()</strong> işlevinde çoklu sorgu
  yürütmesini devre dışı bırakır.
  
  Bu sabitin, yeni bir veritabanı tanıtıcısı oluştururken yalnızca <strong>$driver_options</strong> dizisinde
  kullanılabileceğini unutmayın.


id: PDO::MYSQL_ATTR_READ_DEFAULT_FILE
type: constant
doc:
<comment>Description:</comment>
  Seçenekler my.cnf yerine burada belirtilen dosyadan okunur. Bu seçenek, mysqlnd ile kullanılamaz,
  çünkü mysqlnd, mysql yapılandırma dosyalarını okumaz.


id: PDO::MYSQL_ATTR_READ_DEFAULT_GROUP
type: constant
doc:
<comment>Description:</comment>
  Seçenekler my.cnf dosyasında belirtilen gruptan veya <info>MYSQL_READ_DEFAULT_FILE</info> ile belirtilen
  dosyadan okunur. Bu seçenek, mysqlnd ile kullanılamaz, çünkü mysqlnd, mysql yapılandırma
  dosyalarını okumaz.


id: PDO::MYSQL_ATTR_SSL_CAPATH
type: constant
doc:
<comment>Description:</comment>
  PEM biçiminde saklanan güvenilir SSL CA sertifikalarını içeren dizinin dosya yolu.


id: PDO::MYSQL_ATTR_SSL_CIPHER
type: constant
doc:
<comment>Description:</comment>
  OpenSSL tarafından anlaşılan biçemde, SSL şifrelemesi için kullanılmasına izin verilen bir veya
  daha fazla şifrenin listesi. Örnek: <return>DHE-RSA-AES256-SHA:AES128-SHA</return>


id: PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT
type: constant
doc:
<comment>Description:</comment>
  Sunucu SSL sertifikasının doğrulanmasını devre dışı bırakmanın bir yolunu sağlar.
  
  Mevcut olduğu PHP sürümleri:  7.0.18 ve PHP 7.1.4.


id: PDO::MYSQL_ATTR_USE_BUFFERED_QUERY
type: constant
doc:
<comment>Description:</comment>
  Öntanımlı olarak tüm deyimler tamponlu kipte yürütülür. Bir <class>PDO</class> nesnesi üzerinde bu özniteliğe
  <info>false</info> atanırsa MySQL sürücüsü tamponlu kipi kullanır.
  
  -  MySQL sürücüsünde tamponlu kipi zorlamaksetAttribute(PDO::MYSQL_ATTR_USE_BUFFERED_QUERY,
  false);
  
  $unbufferedResult = $pdo->query("SELECT Name FROM City");
  foreach ($unbufferedResult as $row) { echo $row['Name'] . PHP_EOL;
  }
  ?>
  ]]>


id: PDO::OCI_ATTR_ACTION
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the action on the database session.
  
  Mevcut olduğu PHP sürümleri:  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_CLIENT_IDENTIFIER
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the client identifier on the database session.
  
  Mevcut olduğu PHP sürümleri:  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_CLIENT_INFO
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the client info on the database session.
  
  Mevcut olduğu PHP sürümleri:  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_MODULE
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the module on the database session.
  
  Mevcut olduğu PHP sürümleri:  7.2.16 and 7.3.3


id: PDO::ODBC_ATTR_ASSUME_UTF8
type: constant
doc:
<comment>Description:</comment>
  Windows only. If <info>true</info>, UTF-16 encoded character data (<return>CHAR</return>, <return>VARCHAR</return> and <return>LONGVARCHAR</return>) is converted
  to UTF-8 when reading from or writing data to the database. If <info>false</info> (the default), character
  encoding conversion may be done by the driver.


id: PDO::ODBC_ATTR_USE_CURSOR_LIBRARY
type: constant
doc:
<comment>Description:</comment>
  This option controls whether the ODBC cursor library is used. The ODBC cursor library supports
  some advanced ODBC features (e.g. block scrollable cursors), which may not be implemented by the
  driver. The following values are supported: <info>PDO::ODBC_SQL_USE_IF_NEEDED</info> (the default): use the
  ODBC cursor library when needed. <info>PDO::ODBC_SQL_USE_DRIVER</info>: never use the ODBC cursor library.
  <info>PDO::ODBC_SQL_USE_ODBC</info>: always use the ODBC cursor library.
  
  <info>PDO::ODBC_SQL_USE_IF_NEEDED</info> (the default): use the ODBC cursor library when needed.
  
  <info>PDO::ODBC_SQL_USE_DRIVER</info>: never use the ODBC cursor library.
  
  <info>PDO::ODBC_SQL_USE_ODBC</info>: always use the ODBC cursor library.


id: PDO::PARAM_EVT_FETCH_POST
type: constant
doc:
<comment>Description:</comment>
  Bir sonuç kümesinden bir sonucun alınmasının ardından tetiklenen olay.


id: PDO::PARAM_EVT_FETCH_PRE
type: constant
doc:
<comment>Description:</comment>
  Bir sonuç kümesinden bir sonucun alınmasından önce tetiklenen olay.


id: PDO::PARAM_EVT_NORMALIZE
type: constant
doc:
<comment>Description:</comment>
  Sürücünün bağımsız değişken isminin normalleştirilmesini sağlamak için ilişkili bağımsız
  değişkenin kayda geçirilmesi sırasında tetiklenen olay.


id: PDO::PARAM_INPUT_OUTPUT
type: constant
doc:
<comment>Description:</comment>
  Bağımsız değişkenin bir saklı yordam için bir girdi/çıktı bağımsız değişkeni olduğunu gösterir. Bu
  değeri bir PDO::PARAM_* veri türü ile bit seviyesinde VEYAlamanız gerekir.


id: PDO::PARAM_STMT
type: constant
doc:
<comment>Description:</comment>
  Kayıt kümesi (recordset) türünü ifade eder. Her sürücü desteklemez.


id: PDO::PARAM_STR_CHAR
type: constant
doc:
<comment>Description:</comment>
  Dizgenin normal karakter kümesini kullanacağını belirtir.
  
  PHP 7.2.0'dan beri kullanılabilir.


id: PDO::PARAM_STR_NATL
type: constant
doc:
<comment>Description:</comment>
  Dizgenin ulusal karakter kümesini kullanacağını belirtir.
  
  PHP 7.2.0'dan beri kullanılabilir.


id: PDO::PGSQL_ATTR_DISABLE_PREPARES
type: constant
doc:
<comment>Description:</comment>
  Send the query and the parameters to the server together in a single call, avoiding the need to
  create a named prepared statement separately. If the query is only going to be executed once this
  can reduce latency by avoiding an unnecessary server round-trip.


id: PDO::SQLITE_DETERMINISTIC
type: constant
doc:
<comment>Description:</comment>
  PDO::sqliteCreateFunction ile oluşturulan işlevin belirlenimsel olduğunu belirtir. Yani SQL
  deyiminin belli bir girdi için daima belli bir sonucu döndüreceğini belirtir. (PHP 7.1.4 ve
  sonrasında mevcuttur.)


id: PDO::SQLSRV_ATTR_DIRECT_QUERY
type: constant
doc:
<comment>Description:</comment>
  Indicates that a query should be executed directly, without being prepared.  This constant can be
  passed to PDO::setAttribute, and PDO::prepare. For more  information, see  Direct and Prepared
  Statement Execution.


id: PDO::SQLSRV_ATTR_QUERY_TIMEOUT
type: constant
doc:
<comment>Description:</comment>
  A non-negative integer representing the timeout period, in seconds. Zero (0)  is the default and
  means no timeout. This constant can be passed to  PDOStatement::setAttribute, PDO::setAttribute,
  and PDO::prepare.


id: PDO::SQLSRV_ENCODING_BINARY
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved as a raw byte stream to/from the server  without performing
  encoding or translation. This constant can be passed to  PDOStatement::setAttribute, PDO::prepare,
  PDOStatement::bindColumn, and  PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server according to  PDO::SQLSRV_ENCODING_SYSTEM
  if specified during connection. The connection's  encoding is used if specified in a prepare
  statement. This constant can be  passed to PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_SYSTEM
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server as 8-bit characters  as specified in the
  code page of the Windows locale that is set on the system.  Any multi-byte characters or
  characters that do not map into this code page  are substituted with a single byte question mark
  (?) character. This constant  can be passed to PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_UTF8
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server in UTF-8 encoding.  This is the default
  encoding. This constant can be passed to  PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_TXN_READ_COMMITTED
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Read Committed.


id: PDO::SQLSRV_TXN_READ_UNCOMMITTED
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Read Uncommitted.


id: PDO::SQLSRV_TXN_REPEATABLE_READ
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Repeateable Read.


id: PDO::SQLSRV_TXN_SERIALIZABLE
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Serializable.


id: PDO::SQLSRV_TXN_SNAPSHOT
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to Snapshot.


id: PDO::__construct
type: function
doc:
<comment>Description:</comment>
  Bir veritabanı bağlantısını temsil eden bir PDO nesnesi
    oluşturur
  
  Belirtilen veritabanına kurulan bağlantıyı temsil eden bir PDO nesnesi oluşturur.

<comment>Param:</comment>
  <info>string</info>       <strong>$dsn</strong>         Veritabanına bağlantı için gerekli bilgiyi içeren veri kaynağının ismi.
                            
                            Genellikle bir veri kaynağı ismi, aralarında bir noktalı virgül bulunan
                            sürücü ismi ile PDO sürücüsüne özgü bağlantı sözdiziminden oluşur. Bu
                            konuda daha ayrıntılı bilgiyi  sayfasında bulabilirsiniz.
                            
                            <strong>$dsn</strong> bağımsız değişkeni, bir veritabanı bağlantısı oluşturmak için
                            gereken üç farklı yöntemi destekler:
                            
                            Sürücü isteği<strong>$dsn</strong> bağımsız değişkeni, veri kaynağı ismi için gereken
                            herşeyi içerir. URI isteği<strong>$dsn</strong> bağımsız değişkeni, uri: sözcüğünü
                            takibeden, veri kaynağı isim dizgesini içeren bir dosyanın yerini
                            belirten bir özkaynak betimleyicisi içerir.
                            uri:file:///bir/yol/dsndosyasıTakma ad kullanımı<strong>$dsn</strong> bağımsız değişkeni,
                            php.ini içinde DSN dizgesini tanımlayan pdo.dsn.<strong>$isim</strong> ile eşleşen <strong>$isim</strong>
                            adını içerir.  Takma ad, .htaccess veya httpd.conf dosyasında değil
                            php.ini dosyasında tanımlanmış olmalıdır.
                            
                            <strong>$dsn</strong> bağımsız değişkeni, veri kaynağı ismi için gereken herşeyi içerir.
                            
                            <strong>$dsn</strong> bağımsız değişkeni, uri: sözcüğünü takibeden, veri kaynağı isim
                            dizgesini içeren bir dosyanın yerini belirten bir özkaynak betimleyicisi
                            içerir.
                            
                            uri:file:///bir/yol/dsndosyası
                            
                            <strong>$dsn</strong> bağımsız değişkeni, php.ini içinde DSN dizgesini tanımlayan
                            pdo.dsn.<strong>$isim</strong> ile eşleşen <strong>$isim</strong> adını içerir.
                            
                            Takma ad, .htaccess veya httpd.conf dosyasında değil php.ini dosyasında
                            tanımlanmış olmalıdır.
  <info>string</info>       <strong>$dsn</strong>         <strong>$dsn</strong> bağımsız değişkeni, veri kaynağı ismi için gereken herşeyi içerir.
  <info>string</info>       <strong>$dsn</strong>         <strong>$dsn</strong> bağımsız değişkeni, uri: sözcüğünü takibeden, veri kaynağı isim
                            dizgesini içeren bir dosyanın yerini belirten bir özkaynak betimleyicisi
                            içerir.
                            
                            uri:file:///bir/yol/dsndosyası
  <info>string</info>       <strong>$dsn</strong>         <strong>$dsn</strong> bağımsız değişkeni, php.ini içinde DSN dizgesini tanımlayan
                            pdo.dsn.<strong>$isim</strong> ile eşleşen <strong>$isim</strong> adını içerir.
                            
                            Takma ad, .htaccess veya httpd.conf dosyasında değil php.ini dosyasında
                            tanımlanmış olmalıdır.
  <info>string|null</info>  <strong>$kullanıcı</strong>  DSN dizgesi için kullanıcı ismi. Bu bağımsız değişkenin belirtilmesi
                            bazı PDO sürücüleri için isteğe bağlıdır.
  <info>string|null</info>  <strong>$parola</strong>      DSN dizgesi için parola. Bu bağımsız değişkenin belirtilmesi bazı PDO
                            sürücüleri için isteğe bağlıdır.
  <info>array|null</info>   <strong>$seçenekler</strong>  Sürücüye özgü bağlantı seçeneklerini içeren bir isim=&gt;değer çiftleri
                            dizisi.


id: PDO::beginTransaction
type: function
doc:
<comment>Description:</comment>
  Bir toplu hareketi ilklendirir
  
  Ototeslim kipini kapatır. Otomatik kip kapalıyken PDO nesne örneği üzerinden veritabanında yapılan
  değişiklikler PDO::commit çağrısı ile toplu hareket tamamlanmadan veritabanında bir değişikliğe
  yol açmaz. Toplu hareketlerle yapılan değişiklikleri geri almak ve tekrar otomatik kipe dönmek
  için PDO::rollBack yöntemini kullanabilirsiniz.
  
  MySQL dahil bazı veritabanları, bir toplu hareketin içinde DROP TABLE veya CREATE TABLE gibi bir
  veritabanı tanımlama dili deyimi kullanıldığında otomatik olarak örtük bir PDO::commit yaparlar.
  Örtük PDO::commit, toplu hareket içindeki diğer değişikliklerin de geri alınmasına engeller.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::commit
   * PDO::rollBack
   * Hareketler ve
    Ototeslim


id: PDO::commit
type: function
doc:
<comment>Description:</comment>
  Bir toplu hareketi veritabanına gönderir
  
  Bir toplu hareketi veritabanına gönderir ve bir PDO::beginTransaction çağrısı ile yeni bir toplu
  hareket başlatılıncaya kadar geçerli olmak üzere bağlantıyı ototeslim kipine sokar.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::beginTransaction
   * PDO::rollBack


id: PDO::cubrid_schema
type: function
doc:
<comment>Description:</comment>
  Get the requested schema information
  
  This function is used to get the requested schema information from database. You have to designate
  <strong>$table_name</strong>, if you want to get information on certain table, <strong>$col_name</strong>, if you want to get
  information on certain column (can be used only with PDO::CUBRID_SCH_COL_PRIVILEGE).
  
  The result of this function is returned as a two-dimensional array (column (associative array) *
  row (numeric array)). The following tables shows types of schema and the column structure of the
  result array to be returned based on the schema type.
  
  Result Composition of Each TypeSchemaColumn NumberColumn
  NameValuePDO::CUBRID_SCH_TABLE1NAME2TYPE0:system table 1:view
  2:tablePDO::CUBRID_SCH_VIEW1NAME2TYPE1:viewPDO::CUBRID_SCH_QUERY_SPEC1QUERY_SPECPDO::CUBRID_SCH_ATTRIBUTE
  / PDO::CUBRID_SCH_TABLE_ATTRIBUTE1ATTR_NAME2DOMAIN3SCALE4PRECISION5INDEXED1:indexed6NOT NULL1:not
  null7SHARED1:shared8UNIQUE1:unique9DEFAULT10ATTR_ORDERbase:111CLASS_NAME12SOURCE_CLASS13IS_KEY1:keyPDO::CUBRID_SCH_METHOD
  /
  PDO::CUBRID_SCH_TABLE_METHOD1NAME2RET_DOMAIN3ARG_DOMAINPDO::CUBRID_SCH_METHOD_FILE1METHOD_FILEPDO::CUBRID_SCH_SUPER_TABLE
  / PDO::CUBRID_SCH_DIRECT_SUPER_TABLE / PDO::CUBRID_SCH_SUB_TABLE1CLASS_NAME2TYPE0:system table
  1:view 2:tablePDO::CUBRID_SCH_CONSTRAINT1TYPE0:unique 1:index 2:reverse unique 3:reverse
  index2NAME3ATTR_NAME4NUM_PAGES5NUM_KEYS6PRIMARY_KEY1:primary
  key7KEY_ORDERbase:1PDO::CUBRID_SCH_TRIGGER1NAME2STATUS3EVENT4TARGET_CLASS5TARGET_ATTR6ACTION_TIME7ACTION8PRIORITY9CONDITION_TIME10CONDITIONPDO::CUBRID_SCH_TABLE_PRIVILEGE
  / PDO::CUBRID_SCH_COL_PRIVILEGE1CLASS_NAME /
  ATTR_NAME2PRIVILEGE3GRANTABLEPDO::CUBRID_SCH_PRIMARY_KEY1CLASS_NAME2ATTR_NAME3KEY_SEQbase:14KEY_NAMEPDO::CUBRID_SCH_IMPORTED_KEYS
  / PDO::CUBRID_SCH_EXPORTED_KEYS /
  PDO::CUBRID_SCH_CROSS_REFERENCE1PKTABLE_NAME2PKCOLUMN_NAME3FKTABLE_NAMEbase:14FKCOLUMN_NAME5KEY_SEQbase:16UPDATE_ACTION0:cascade
  1:restrict 2:no action 3:set null7DELETE_ACTION0:cascade 1:restrict 2:no action 3:set
  null8FK_NAME9PK_NAME

<comment>Param:</comment>
  <info>int</info>     <strong>$schema_type</strong>  Schema type that you want to know.
  <info>string</info>  <strong>$table_name</strong>   Table you want to know the schema of.
  <info>string</info>  <strong>$col_name</strong>     Column you want to know the schema of.

<comment>Return:</comment>
  <info>array</info>  Array containing the schema information, when process is successful;
         
         FALSE, when process is unsuccessful


id: PDO::errorCode
type: function
doc:
<comment>Description:</comment>
  Veritabanındaki son işlemle ilgili SQLSTATE kodunu döndürür

<comment>Return:</comment>
  <info>string|null</info>  ANSI SQL-92 standardında tanımlanan beş karakterlik abecesayısal bir hata tanıtıcısı
               (SQLSTATE) döndürür. Bir SQLSTATE iki karakterlik ana hata sınıfı değerinin ardına
               eklenmiş üç karakterlik alt sınıf değerinden oluşur. 01 ana sınıf değeri bir uyarı
               belirtir ve SQL_SUCCESS_WITH_INFO dönüş kodu ile birlikte bulunur. '01' ve 'IM'
               sınıfları dışındaki tüm sınıf değerleri bir hata belirtir. 'IM' sınıfı PDO
               gerçekleniminden (ve ODBC sürücüsünü kullanıyorsanız ODBC'den) türetilen uyarılar ve
               hatalar ile ilgilidir. Herhangi bir sınıfın '000' alt sınıf değeri o SQLSTATE için
               bir alt sınıfın olmadığını belirtir.
               
               PDO::errorCode sadece doğrudan veritabanı tanıtıcısında yürütülen işlemlerin hata
               kodlarını döndürür. PDO::prepare veya PDO::query ile bir <class>PDOStatement</class> nesnesi
               oluşturup deyim tanıtıcısı üzerinde oluşan bir hatayla ilgili bilgi alacaksanız
               PDOStatement::errorInfo yöntemini kullanmalısınız.
               
               Veritabanı tanıtıcısında yürütülmüş bir işlem yoksa <info>null</info> döner.

<comment>See Also:</comment>
   * PDO::errorInfo
   * PDOStatement::errorCode
   * PDOStatement::errorInfo


id: PDO::errorInfo
type: function
doc:
<comment>Description:</comment>
  Veritabanındaki son işlemle ilgili hata bilgisini döndürür
    
  
  Veritabanındaki son işlemle ilgili hata bilgisini döndürür.

<comment>Return:</comment>
  <info>array</info>  Veritabanındaki son işlemle ilgili hata bilgisini içeren bir dizi döndürür. Dizi en azından
         şu alanları içerir: ElemanBilgi0SQLSTATE hata kodu (ANSI SQL standardında tanımlanmış beş
         karakterlik abecesayısal bir tanıtıcı).1Sürücüye özgü hatanın kodu.2Sürücüye özgü hatanın
         iletisi.
         
         SQLSTATE hata kodu atanmamışsa veya sürücüye özgü hata kodu yoksa 0. eleman hariç bütün
         elemanlar <info>null</info> içerir.
         
         PDO::errorInfo yöntemi sadece veritabanına doğrudan uygulanan işlemlerin hata bilgisini
         döndürür. PDO::prepare veya PDO::query ile bir <class>PDOStatement</class> nesnesi oluşturup deyim
         tanıtıcısı üzerinde oluşan bir hatayla ilgili bilgi alacaksanız PDOStatement::errorInfo
         yöntemini kullanmalısınız.

<comment>See Also:</comment>
   * PDO::errorCode
   * PDOStatement::errorCode
   * PDOStatement::errorInfo


id: PDO::exec
type: function
doc:
<comment>Description:</comment>
  Belirtilen SQL deyimini çalıştırır ve etkilenen satır sayısını
    döndürür
  
  PDO::exec belirtilen SQL deyimini tek bir işlev çağrısıyla çalıştırır ve deyimden etkilenen
  satırların sayısını döndürür.
  
  PDO::exec yöntemi bir SELECT deyiminin sonucunu döndürmez. Bir SELECT deyimini uygulamanız boyunca
  sadece bir defa çalıştıracaksanız PDO::query yöntemini kullanabilirsiniz. Defalarca
  çalıştıracaksanız PDO::prepare ile bir <class>PDOStatement</class> nesnesi hazırlayıp  bunu PDOStatement::execute
  ile çalıştırabilirsiniz.

<comment>Param:</comment>
  <info>string</info>  <strong>$deyim</strong>  Hazırlanıp çalıştırılacak SQL deyimi.
                  
                  Sorgunun içindeki verinin gerektiği gibi öncelenmesi gerekir.

<comment>Return:</comment>
  <info>int|false</info>  PDO::exec işlevi çalıştırılan SQL deyimiyle silinen veya değiştirilen satırların
             sayısını döndürür. Etkilenen satır yoksa   PDO::exec <return>0</return> döndürür.
             
             Bu işlev mantıksal <info>false</info>
             değeriyle dönebileceği gibi <info>false</info> olarak değerlendirilebilecek mantıksal
             olmayan bir değerle de dönebilir. Bu konuda daha fazla bilgi
             Mantıksal Değerler bölümünde
             bulunabilir. Bu işlevden dönen değeri sınamak için
             <return>===</return>
             işleci kullanılabilir.
             
             Aşağıda, dönüş değerinin yanlış ele alındığı bir örneğe yer verilmiştir. Etkilenen
             satır sayısı 0 olduğu halde <strong>die()</strong> işlevi çağrılmaktadır: exec() or
             die(print_r($db->errorInfo(), true));// yanlış
             ?>
             ]]>

<comment>See Also:</comment>
   * PDO::prepare
   * PDO::query
   * PDOStatement::execute


id: PDO::getAttribute
type: function
doc:
<comment>Description:</comment>
  Bir veritabanı bağlantı özniteliğinin değerini döndürür
    
  
  Bir veritabanı bağlantı özniteliğinin değerini döndürür.
  
  Bazı veritabanı/sürücü çiftlerinin veritabanı bağlantı özniteliklerinin tamamını
  desteklemeyebileceği unutulmamalıdır.

<comment>Param:</comment>
  <info>int</info>  <strong>$öznitelik</strong>  <return>PDO::ATTR_*</return> sabitlerinden biri. Sabitlerin açıklamaları için  sayfasında
                   bulunabilir. Veritabanı bağlantılarına uygulanabilecek sürücüye özgü sabitler:
                   <return>PDO::ATTR_AUTOCOMMIT</return><return>PDO::ATTR_CASE</return><return>PDO::ATTR_CLIENT_VERSION</return><return>PDO::ATTR_CONNECTION_STATUS</return><return>PDO::ATTR_DRIVER_NAME</return><return>PDO::ATTR_ERRMODE</return><return>PDO::ATTR_ORACLE_NULLS</return><return>PDO::ATTR_PERSISTENT</return><return>PDO::ATTR_PREFETCH</return><return>PDO::ATTR_SERVER_INFO</return><return>PDO::ATTR_SERVER_VERSION</return><return>PDO::ATTR_TIMEOUT</return>
                   
                   Bazı sürücüler sürücüye özgü "ek" öznitelikleri kullanamayabilir. Sürücüye özgü
                   özniteliklerin başka sürücülerde kullanılmamasına ise özellikle dikkat
                   edilmelidir.

<comment>Return:</comment>
  <info>mixed</info>  Başarısızlık durumunda <info>null</info> yoksa istenen PDO özniteliğinin değerini döndürür.

<comment>See Also:</comment>
   * PDO::setAttribute
   * PDOStatement::getAttribute
   * PDOStatement::setAttribute


id: PDO::getAvailableDrivers
type: function
doc:
<comment>Description:</comment>
  Kullanılabilen PDO sürücülerini içeren bir dizi döndürür
    
  
  PDO::__construct yönteminin <strong>$DSN</strong> bağımsız değişkeninde kullanılabilen PDO sürücülerinin listesini
  döndürür.

<comment>Return:</comment>
  <info>array</info>  PDO::getAvailableDrivers yöntemi PDO sürücü isimlerini içeren bir dizi döndürür. Hiç sürücü
         yoksa boş bir dizi döner.


id: PDO::inTransaction
type: function
doc:
<comment>Description:</comment>
  Checks if inside a transaction
    
  
  Checks if a transaction is currently active within the driver. This method only works for database
  drivers that support transactions.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if a transaction is currently active, and <info>false</info> if not.


id: PDO::lastInsertId
type: function
doc:
<comment>Description:</comment>
  Son yerleştirilen satırın veya sıradaki değerin kimliğini döndürür
  
  Sürücüye bağlı olarak, yerleştirilen son satırın veya bir sıralama nesnesindeki son değerin
  kimliğini döndürür. Örneğin, PDO_PGSQL <strong>$isim</strong> bağımsız değişkeninde bir sıralama nesnesi ismi
  belirtilmesini gerektirir.
  
  Bu yöntem, sıralı veya otomatik artan alanlarla ilgili desteğin bulunmadığı veritabanları için
  anlamlı veya tutarlı bir sonuç döndüremeyebilir.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$isim</strong>  Kimliği döndürülecek sırama nesnesinin ismi.

<comment>Return:</comment>
  <info>string|false</info>  <strong>$isim</strong> bağımsız değişkeninde bir sıralama nesnesi ismi belirtilmezse
                PDO::lastInsertId, veritabanına son yerleştirilen satırın satır kimliğini bir dizge
                olarak döndürür.
                
                <strong>$isim</strong> bağımsız değişkeninde bir sıralama nesnesi ismi belirtilmişse
                PDO::lastInsertId, sıralama nesnesinden alınan son değeri ifade eden bir dizge
                döndürür.
                
                PDO sürücüsü bu özelliği desteklemiyorsa PDO::lastInsertId bir <return>IM001</return> durumu
                (SQLSTATE) tetikler.


id: PDO::pgsqlCopyFromArray
type: function
doc:
<comment>Description:</comment>
  Copy data from PHP array into table
  
  Copies data from <strong>$rows</strong> array to table <strong>$table_name</strong> using <strong>$delimiter</strong> as fields delimiter and <strong>$fields</strong>
  list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>array</info>   <strong>$rows</strong>        Array of strings with fields separated by <strong>$delimiter</strong>
  <info>string</info>  <strong>$delimiter</strong>   Delimiter used in <strong>$rows</strong> array
  <info>string</info>  <strong>$null_as</strong>     How to interpret null values
  <info>string</info>  <strong>$fields</strong>      List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, başarısızlık durumunda <info>false</info> döner.


id: PDO::pgsqlCopyFromFile
type: function
doc:
<comment>Description:</comment>
  Copy data from file into table
  
  Copies data from file specified by <strong>$filename</strong> into table <strong>$table_name</strong> using <strong>$delimiter</strong> as fields
  delimiter and <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$filename</strong>    Filename containing data to import
  <info>string</info>  <strong>$delimiter</strong>   Delimiter used in file specified by <strong>$filename</strong>
  <info>string</info>  <strong>$null_as</strong>     How to interpret null values
  <info>string</info>  <strong>$fields</strong>      List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, başarısızlık durumunda <info>false</info> döner.


id: PDO::pgsqlCopyToArray
type: function
doc:
<comment>Description:</comment>
  Copy data from database table into PHP array
  
  Copies data from <strong>$table</strong> into array using <strong>$delimiter</strong> as fields delimiter and <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$delimiter</strong>   Delimiter used in rows
  <info>string</info>  <strong>$null_as</strong>     How to interpret null values
  <info>string</info>  <strong>$fields</strong>      List of fields to export

<comment>Return:</comment>
  <info>array|false</info>  Returns an array of rows, başarısızlık durumunda <info>false</info> döner.


id: PDO::pgsqlCopyToFile
type: function
doc:
<comment>Description:</comment>
  Copy data from table into file
  
  Copies data from table into file specified by <strong>$filename</strong> using <strong>$delimiter</strong> as fields delimiter and
  <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$filename</strong>    Filename to export data
  <info>string</info>  <strong>$delimiter</strong>   Delimiter used in file specified by <strong>$filename</strong>
  <info>string</info>  <strong>$null_as</strong>     How to interpret null values
  <info>string</info>  <strong>$fields</strong>      List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, başarısızlık durumunda <info>false</info> döner.


id: PDO::pgsqlGetNotify
type: function
doc:
<comment>Description:</comment>
  Get asynchronous notification
  
  Returns a result set representing a pending asynchronous notification.

<comment>Param:</comment>
  <info>int</info>  <strong>$result_type</strong>  The format the result set should be returned as, represented as a <info>PDO::FETCH_*</info>
                     constant.
  <info>int</info>  <strong>$ms_timeout</strong>   The length of time to wait for a response, in milliseconds.

<comment>Return:</comment>
  <info>array|false</info>  If one or more notifications is pending, returns a single row, with fields <return>message</return>
               and <return>pid</return>, otherwise returns <info>false</info>.


id: PDO::pgsqlGetPid
type: function
doc:
<comment>Description:</comment>
  Get the server PID
  
  Returns the server's PID.

<comment>Return:</comment>
  <info>int</info>  The server's PID.


id: PDO::pgsqlLOBCreate
type: function
doc:
<comment>Description:</comment>
  Creates a new large object
  
  <strong>PDO::pgsqlLOBCreate()</strong> creates a large object and returns the OID of that object.  You may then
  open a stream on the object using <strong>PDO::pgsqlLOBOpen()</strong> to read or write data to it.  The OID can be
  stored in columns of type OID and be used to reference the large object, without causing the row
  to grow arbitrarily large. The large object will continue to live in the database until it is
  removed by calling <strong>PDO::pgsqlLOBUnlink()</strong>.
  
  Large objects can be up to 2GB in size, but are cumbersome to use; you need to ensure that
  <strong>PDO::pgsqlLOBUnlink()</strong> is called prior to deleting the last row that references its OID from your
  database. In addition, large objects have no access controls.  As an alternative, try the bytea
  column type; recent versions of PostgreSQL allow bytea columns of up to 1GB in size and
  transparently manage the storage for optimal row size.
  
  This function must be called within a transaction.

<comment>Return:</comment>
  <info>string</info>  Returns the OID of the newly created large object on success, or <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>PDO::pgsqlLOBOpen()</strong>
   * <strong>PDO::pgsqlLOBUnlink()</strong>
   * <strong>pg_lo_create()</strong>


id: PDO::pgsqlLOBOpen
type: function
doc:
<comment>Description:</comment>
  Opens an existing large object stream
  
  <strong>PDO::pgsqlLOBOpen()</strong> opens a stream to access the data referenced by <strong>$oid</strong>.  If <strong>$mode</strong> is <return>r</return>, the
  stream is opened for reading, if <strong>$mode</strong> is <return>w</return>, then the stream will be opened for writing.  You can
  use all the usual filesystem functions, such as <strong>fread()</strong>, <strong>fwrite()</strong> and <strong>fgets()</strong> to manipulate the
  contents of the stream.
  
  This function, and all manipulations of the large object, must be called and carried out within a
  transaction.

<comment>Param:</comment>
  <info>string</info>  <strong>$oid</strong>   A large object identifier.
  <info>string</info>  <strong>$mode</strong>  If mode is <return>r</return>, open the stream for reading. If mode is <return>w</return>, open the stream for
                 writing.

<comment>Return:</comment>
  <info>resource|false</info>  Returns a stream resource on success başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PDO::pgsqlLOBCreate()</strong>
   * <strong>PDO::pgsqlLOBUnlink()</strong>
   * <strong>pg_lo_open()</strong>


id: PDO::pgsqlLOBUnlink
type: function
doc:
<comment>Description:</comment>
  Deletes the large object
  
  Deletes a large object from the database identified by OID.
  
  This function must be called within a transaction.

<comment>Param:</comment>
  <info>string</info>  <strong>$oid</strong>  A large object identifier

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PDO::pgsqlLOBOpen()</strong>
   * <strong>PDO::pgsqlLOBCreate()</strong>


id: PDO::prepare
type: function
doc:
<comment>Description:</comment>
  Çalıştırılmak üzere bir deyimi hazırlar ve bir deyim nesnesi olarak döndürür
  
  PDOStatement::execute yöntemi ile çalıştırılmak üzere bir SQL deyimi hazırlar. Deyim şablonu sıfır
  veya daha fazla sayıda birer isimle (:isim) veya birer soru imi (?) ile ifade edilen bağımsız
  değişken içerebilir. Deyimin çalıştırılması sırasında bu bağımsız değişkenlere farklı değerler
  atanarak aynı deyim defalarca kullanılabilir. Aynı deyim şablonunda hem isimli hem de soru imli
  bağımsız değişkenleri kullanamazsınız. İkisinden birini seçmek zorundasınız. Herhangi bir
  kullanıcı girişini bağlamak için bu bağımsız değişkenleri kullanın, kullanıcı girişini doğrudan
  sorguya dahil etmeyin.
  
  PDOStatement::execute işlevinde aktaracağınız her değer için eşsiz bir bağımsız değişken imleyici
  belirtmelisiniz. Öykünme kipi açık olmadığı sürece, hazırlanmış bir ifadede aynı ismi birden fazla
  isimli bağımsız değişken işaretçisinde kullanamazsınız.
  
  Bağımsız değişken işaretçileri yalnızca eksiksiz bir değişmez veriyi temsil edebilir. Ne değişmez
  parçasının, ne anahtar sözcük, ne tanımlayıcı ne de herhangi bir keyfi sorgu parçasının bağımsız
  değişken kullanılarak bağlanması mümkün değildir. Örneğin, bir SQL ifadesinin IN() yan tümcesinde
  tek bir bağımsız değişkene birden çok değer bağlayamazsınız.
  
  Bir SQL deyiminin farklı değerlerle defalarca çalıştırılmak üzere PDO::prepare ve
  PDOStatement::execute yöntemlerine aktarılması, bu SQL deyimiyle ilgili sorgu planının ve temel
  verilerin müzakere edilmek üzere sürücü tarafından istemci ve/veya sunucu tarafında
  önbelleklemesiyle uygulamanızın başarımını yükseltecek en iyilemelerin yapılması mümkün olur.
  Ayrıca, PDO::prepare ve PDOStatement::execute işlevlerinin kullanımı, bağımsız değişkenlerin elle
  öncelenmesi gereğini ortadan kaldırarak SQL zerk saldırılarını engellemeye yardımcı olur.
  
  Bağımsız değişkenli hazır deyimlerin değerlerle ilişkilendirilmesi işlemini desteklemeyen
  sürücüler için PDO bu işlemi taklit eder. Ayrıca sürücü isimli ve soru imli bağımsız değişken
  aktarım tarzlarından yalnız birini destekliyorsa PDO diğer tarzı da taklit eder.
  
  Öykünülmüş hazırlanmış ifadeler ve isimli veya soru işareti tarzı bağımsız değişkenlerinin yeniden
  yazılması için kullanılan çözümleyici, tek ve çift tırnaklar için standart olmayan tersbölülü
  öncelemeyi destekler. Bu, bir tersbölü ile öncelenmiş sonlandırma tırnaklarında bu kullanımın
  desteklenmediği anlamına gelir, bu da bağımsız değişkenlerin yanlış algılanmasına neden olarak
  hazırlanan ifadenin yürütüldüğünde başarısız olmasına sebep olabilir. Çözüm, bu tür SQL sorguları
  için öykünülmüş hazırlıklar kullanmamak ve sürücü tarafından yerel olarak desteklenen bir bağımsız
  değişken tarzı kullanarak bağımsız değişkenlerin yeniden yazılmasını önlemektir.
  
  PHP 7.4.0 ve sonrasında, soru imleri kendileri ile öncelenebiliyor. Yani, <return>??</return> dizgesi artık
  veritabanına <return>?</return> dizgesi olartak gönderiliyor.

<comment>Param:</comment>
  <info>string</info>  <strong>$deyim</strong>       Hedef veritabanı sunucusu için geçerli bir SQL deyimi şablonu olmalıdır.
  <info>array</info>   <strong>$seçenekler</strong>  Bu yöntemden döndürülen <class>PDOStatement</class> nesnesi için atanacak öznitelik
                       değerlerini isim=&gt;değer çiftleri halinde içeren bir dizi. Çoğunlukla
                       kaydırılabilen bir gösterici isteği için <return>PDO::CURSOR_SCROLL</return> özniteliğine
                       <return>PDO::ATTR_CURSOR</return> değerini atamakta kullanılır. Bazı sürücülerin deyimin
                       hazırlanması aşamasında atanabilen sürücüye özgü öznitelikleri vardır.

<comment>Return:</comment>
  <info>PDOStatement|false</info>  Veritabanı sunucusu deyimi başarıyla hazırlayabilmişse PDO::prepare bir
                      <class>PDOStatement</class> nesnesi döndürür; aksi takdirde ya bir <class>PDOException</class> yavrulanır
                      veya işlev <info>false</info> döndürür (hata işlemeye bağımlı olarak).
                      
                      Öykünülmüş hazır deyimler için veritabanı sunucusuyla müzakere yapılmadığından
                      PDO::prepare deyim üzerinde bir sınama yapmaz.

<comment>See Also:</comment>
   * PDO::exec
   * PDO::query
   * PDOStatement::execute


id: PDO::query
type: function
doc:
<comment>Description:</comment>
  Bir SQL deyimini yer tutucular olmaksızın hazırlar ve çalıştırır
  
  Bir SQL deyimini tek bir işlev çağrısında çalıştırır ve deyimi bir <class>PDOStatement</class> nesnesi olarak
  döndürür.
  
  Defalarca yineleyeceğiniz bir sorguyu PDO::prepare yöntemini kullanarak bir <class>PDOStatement</class> nesnesi
  haline getirip bunu PDOStatement::execute ile defalarca çalıştırmak başarımı arttıracaktır.
  
  Tekrar bir PDO::query çağrısı yapmadan önce sonuç kümesindeki veriyi almazsanız çağrınız
  başarısızlıkla sonuçlanabilir. Yeni bir PDO::query çağrısını yapmadan önce <class>PDOStatement</class> nesnesi
  ile ilişkilendirilmiş kaynakları serbest bırakmak için PDOStatement::closeCursor çağrısı
  yapmalısınız.
  
  <strong>$deyim</strong> yer tutucular içeriyorsa, deyim PDO::prepare ve PDOStatement::execute yöntemleri
  kullanılarak hazırlanıp çalıştırılmalıdır.

<comment>Param:</comment>
  <info>string</info>    <strong>$deyim</strong>         Hazırlanacak ve çalıştırılacak SQL deyimi.
                           
                           SQL deyimi yer tutucular içeriyorsa, bu yöntem yerine PDO::prepare ve
                           PDOStatement::execute yöntemleri kullanılmalıdır. Veya, SQL deyimi
                           PDO::query çağrılmadan önce elle hazırlanmalı, sürücü destekliyorsa
                           PDO::quote kullanılarak düzgünce öncelenmelidir.
  <info>int|null</info>  <strong>$getirme_kipi</strong>  Döndürülen <class>PDOStatement</class> nesnesi için öntanımlı getirme kipi. <return>PDO::FETCH_*</return>
                           sabitlerinden biri olmalıdır.
                           
                           İşleve fazladan bağımsız değişken aktarılırsa, bunlar sonuç nesnesi
                           üzerinde PDOStatement::setFetchMode çağrısı yapılmış gibi ele alınır.
                           Sonraki bağımsız değişkenler, seçilen getirme kipine bağlı olarak
                           değişir.

<comment>Return:</comment>
  <info>PDOStatement|false</info>  Başarı durumunda <class>PDOStatement</class> nesnesi, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::exec
   * PDO::prepare
   * PDOStatement::execute


id: PDO::quote
type: function
doc:
<comment>Description:</comment>
  Bir sorguda kullanılmak üzere bir dizgeyi önceler
    
  
  Girdi dizgesine gerekiyorsa ilgili veritabanı sürücüsüne uygun bir önceleme uygular.
  
  Bu işlevi SQL deyimlerini oluştururken kullanıyorsanız, kullanıcı girdisini bir SQL deyimi haline
  getirmek için PDO::quote yerine PDO::prepare ile bağımsız değişkenleri ilişkilendirilmiş SQL
  deyimleri hazırlamanızı hararetle öneririz. Bağımsız değişkenlerle ilişkilendirimiş hazır deyimler
  taşınabilir olmaktan başka daha kullanışlı ve SQL zerkine bağışık olmanın yanında sorgunun
  derlenmiş hali hem sunucuda hem de istemcide bulunduğundan yorumlanan sorgulardan çok daha
  hızlıdır.
  
  PDO sürücülerinin hepsi bu yöntemi gerçeklemez. (özellikle PDO_ODBC) Bu bakımdan hazır deyimleri
  kullanmaya hazır olmalısınız.
  
  Karakter kümesi, PDO::quote'u etkilemesi için ya sunucu seviyesinde ya da (sürücüye bağlı olarak)
  veritabanı bağlantısının kendisinde ayarlanmalıdır. Daha fazla bilgi için sürücüye özel belgelere
  bakılabilir.

<comment>Param:</comment>
  <info>string</info>  <strong>$dizge</strong>  Öncelenecek dizge.
  <info>int</info>     <strong>$tür</strong>   İkincil bir önceleme tarzı olan sürücülere veri türü olarak bir ipucu sağlar.
                  Örneğin, <info>PDO_PARAM_LOB</info> sabiti sürücüye ikil veriyi öncelemesini söyler.

<comment>Return:</comment>
  <info>string|false</info>  Bir SQL deyiminde aktarılmak üzere teorik olarak güvenli kabul edilen bir öncelenmiş
                dizge döndürür. Eğer sürücü bu tarz öncelemeyi desteklemiyorsa <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>


id: PDO::rollBack
type: function
doc:
<comment>Description:</comment>
  Bir toplu hareketi geri alır
  
  <strong>PDO::beginTransaction()</strong> ile başlatılan toplu hareketi geri alır.
  
  Eğer veritabanı ototeslim kipindeyse, toplu hareket geri alındıktan sonra tekrar ototeslim kipine
  dönülür.
  
  MySQL dahil bazı veritabanları, bir toplu hareketin içinde DROP TABLE veya CREATE TABLE gibi bir
  veritabanı tanımlama dili deyimi kullanıldığında otomatikman örtük bir PDO::commit yaparlar. Örtük
  PDO::commit, toplu hareket içindeki diğer değişikliklerin de geri alınmasını engeller.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::beginTransaction
   * PDO::commit
   * Hareketler ve
    Ototeslim


id: PDO::setAttribute
type: function
doc:
<comment>Description:</comment>
  Bir öznitelik tanımlar
  
  Veritabanı için bir öznitelik tanımlar. Bazı temel öznitelikler aşağıda listelenmiştir. Bazı
  sürücülerin kendilerine özgü öznitelikleri olabilir. Sürücüye özgü özniteliklerin başka
  sürücülerde kullanılmamasına ise özellikle dikkat edilmelidir. <info>PDO::ATTR_CASE</info> Sütun isimlerinin
  harflerini belli birbüyüklüğe zorlar. Aşağıdaki değerlerden birini alabilir: <info>PDO::CASE_LOWER</info> Sütun
  isimlerinin harflerini küçük harfe zorlar. <info>PDO::CASE_NATURAL</info> Sütun isimlerinin harfleri veritabanı
  sürücüsünden döndüğü haliyle kullanılır. <info>PDO::CASE_UPPER</info> Sütun isimlerinin harflerini büyük harfe
  zorlar. <info>PDO::ATTR_ERRMODE</info> PDO hata raporlama kipi. Aşağıdaki değerlerden birini alabilir:
  <info>PDO::ERRMODE_SILENT</info> Sadece hata kodlarını atar. <info>PDO::ERRMODE_WARNING</info> Bir <info>E_WARNING</info> çıktılanır.
  <info>PDO::ERRMODE_EXCEPTION</info><class>PDOException</class> istisnası yavrulanır. <info>PDO::ATTR_ORACLE_NULLS</info> Sadece Oracle için
  değil, bütün sürücüler için kullanılabilir. <info>null</info>'a ve boş dizgelere dönüşümü belirler. Aşağıdaki
  değerlerden birini alabilir: <info>PDO::NULL_NATURAL</info> Dönüşüm yok. <info>PDO::NULL_EMPTY_STRING</info> Boş dizge
  <info>null</info>'a dönüştürülür. <info>PDO::NULL_TO_STRING</info><info>null</info> boş dizgeye dönüştürülür. <info>PDO::ATTR_STRINGIFY_FETCHES</info>
  Döndürülürken sayısal değerler dizgeye dönüştürülür. Mantıksal bir değer gerekir: <info>true</info>
  etkinleştirir, <info>false</info> iptal eder. <info>PDO::ATTR_STATEMENT_CLASS</info><class>PDOStatement</class> sınıfından türetilmiş
  kullanıcı tanımlı bir deyim sınıfı tanımlar. <return>array(string sınıfadı, array(mixed kurucu_bağımsız
  değişkenler))</return> gerekir.  Kalıcı PDO bağlantılarıyla kullanılamaz. <info>PDO::ATTR_TIMEOUT</info> Zaman aşımı
  süresini saniye cinsinden belirtir. <info>int</info> türünde değer gerektirir.  Tüm sürücüler bu seçeneği
  desteklemez ve anlamı sürücüden sürücüye farklılık gösterebilir. Örneğin, sqlite yazılabilir bir
  kilit almaktan vazgeçmeden önce bu zaman değerini bekler, ancak diğer sürücüler bunu bir bağlanma
  veya okuma zaman aşımı aralığı olarak yorumlayabilir. <info>PDO::ATTR_AUTOCOMMIT</info> Sadece OCI, Firebird ve
  MySQL'de kullanılabilir.  Her tek deyimin otomatik gönderilip gönderilmeyeceği belirtilir.
  Mantıksal bir değer gerekir: <info>true</info> etkinleştirir, <info>false</info> iptal eder. <info>PDO::ATTR_EMULATE_PREPARES</info>
  Sadece OCI, Firebird ve MySQL'de kullanılabilir.  Hazırlanmış deyimlerin öykünmesini etkinleştirir
  veya devre dışı bırakır. Bazı sürücüler yerel olarak hazırlanmış deyimleri desteklemez veya bunlar
  için sınırlı desteğe sahiptir. Mantıksal bir değer gerekir: PDO'yu ya her zaman hazırlanmış
  deyimleri öykünmeye (eğer <info>true</info> ve öykünmüş hazırlar sürücü tarafından destekleniyorsa) ya da yerel
  hazırlanmış deyimleri kullanmaya (<info>false</info> ise) zorlamak için bu ayar kullanılır. Sürücü mevcut
  sorguyu başarılı bir şekilde hazırlayamazsa, her zaman hazırlamış deyimi öykünmeye geri
  dönecektir. <info>PDO::MYSQL_ATTR_USE_BUFFERED_QUERY</info> MySQL'de kullanılır.  Tamponlu sorgu kullanımı.
  Mantıksal bir değer gerekir: <info>true</info> etkinleştirir, <info>false</info> iptal eder. <info>true</info> öntanımlıdır.
  <info>PDO::ATTR_DEFAULT_FETCH_MODE</info> Öntanımlı al-getir kipini ayarlar. Kipin açıklaması için
  <strong>PDOStatement::fetch()</strong> belgesine bakınız.
  
  Sütun isimlerinin harflerini belli birbüyüklüğe zorlar. Aşağıdaki değerlerden birini alabilir:
  
  Sütun isimlerinin harflerini küçük harfe zorlar.
  
  Sütun isimlerinin harfleri veritabanı sürücüsünden döndüğü haliyle kullanılır.
  
  Sütun isimlerinin harflerini büyük harfe zorlar.
  
  PDO hata raporlama kipi. Aşağıdaki değerlerden birini alabilir:
  
  Sadece hata kodlarını atar.
  
  Bir <info>E_WARNING</info> çıktılanır.
  
  <class>PDOException</class> istisnası yavrulanır.
  
  Sadece Oracle için değil, bütün sürücüler için kullanılabilir.
  
  <info>null</info>'a ve boş dizgelere dönüşümü belirler. Aşağıdaki değerlerden birini alabilir:
  
  Dönüşüm yok.
  
  Boş dizge <info>null</info>'a dönüştürülür.
  
  <info>null</info> boş dizgeye dönüştürülür.
  
  Döndürülürken sayısal değerler dizgeye dönüştürülür. Mantıksal bir değer gerekir: <info>true</info>
  etkinleştirir, <info>false</info> iptal eder.
  
  <class>PDOStatement</class> sınıfından türetilmiş kullanıcı tanımlı bir deyim sınıfı tanımlar. <return>array(string
  sınıfadı, array(mixed kurucu_bağımsız değişkenler))</return> gerekir.
  
  Kalıcı PDO bağlantılarıyla kullanılamaz.
  
  Zaman aşımı süresini saniye cinsinden belirtir. <info>int</info> türünde değer gerektirir.
  
  Tüm sürücüler bu seçeneği desteklemez ve anlamı sürücüden sürücüye farklılık gösterebilir.
  Örneğin, sqlite yazılabilir bir kilit almaktan vazgeçmeden önce bu zaman değerini bekler, ancak
  diğer sürücüler bunu bir bağlanma veya okuma zaman aşımı aralığı olarak yorumlayabilir.
  
  Sadece OCI, Firebird ve MySQL'de kullanılabilir.
  
  Her tek deyimin otomatik gönderilip gönderilmeyeceği belirtilir. Mantıksal bir değer gerekir: <info>true</info>
  etkinleştirir, <info>false</info> iptal eder.
  
  Sadece OCI, Firebird ve MySQL'de kullanılabilir.
  
  Hazırlanmış deyimlerin öykünmesini etkinleştirir veya devre dışı bırakır. Bazı sürücüler yerel
  olarak hazırlanmış deyimleri desteklemez veya bunlar için sınırlı desteğe sahiptir. Mantıksal bir
  değer gerekir: PDO'yu ya her zaman hazırlanmış deyimleri öykünmeye (eğer <info>true</info> ve öykünmüş hazırlar
  sürücü tarafından destekleniyorsa) ya da yerel hazırlanmış deyimleri kullanmaya (<info>false</info> ise)
  zorlamak için bu ayar kullanılır. Sürücü mevcut sorguyu başarılı bir şekilde hazırlayamazsa, her
  zaman hazırlamış deyimi öykünmeye geri dönecektir.
  
  MySQL'de kullanılır.
  
  Tamponlu sorgu kullanımı. Mantıksal bir değer gerekir: <info>true</info> etkinleştirir, <info>false</info> iptal eder. <info>true</info>
  öntanımlıdır.
  
  Öntanımlı al-getir kipini ayarlar. Kipin açıklaması için <strong>PDOStatement::fetch()</strong> belgesine bakınız.

<comment>Param:</comment>
  <info>int</info>    <strong>$öznitelik</strong>  Değiştirilecek öznitelik.
  <info>mixed</info>  <strong>$değer</strong>     <strong>$öznitelik</strong>'e atanacak değer. Özniteliğe özgü bir tür gerekli olabilir.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PDO::getAttribute()</strong>
   * <strong>PDOStatement::getAttribute()</strong>
   * <strong>PDOStatement::setAttribute()</strong>


id: PDO::sqliteCreateAggregate
type: function
doc:
<comment>Description:</comment>
  Registers an aggregating User Defined Function for use in SQL statements
    
  
  Bu işlev
  DENEYSELDİR. Bu işlevin davranışı, ismi
  ve belgeleri PHP'nin sonraki sürümlerinde hiçbir duyuru yapılmaksızın
  değiştirilebilir. Bu risk göze alınamayacaksa bu işlev
  kullanılmamalıdır.
  
  This method is similar to  except that it registers functions that can be used to calculate a
  result aggregated across all the rows of a query.
  
  The key difference between this method and  is that two functions are required to manage the
  aggregate.

<comment>Param:</comment>
  <info>string</info>    <strong>$function_name</strong>  The name of the function used in SQL statements.
  <info>callable</info>  <strong>$step_func</strong>      Callback function called for each row of the result set. Your PHP
                            function should accumulate the result and store it in the aggregation
                            context.
                            
                            This function need to be defined as:
                            <info>mixed</info>step<info>mixed</info><strong>$context</strong><info>int</info><strong>$rownumber</strong><info>mixed</info><strong>$value</strong><info>mixed</info><strong>$values</strong> <strong>$context</strong><info>null</info>
                            for the first row; on subsequent rows it will have the value that was
                            previously returned from the step function; you should use this to
                            maintain the aggregate state. <strong>$rownumber</strong> The current row number. <strong>$value</strong>
                            The first argument passed to the aggregate. <strong>$values</strong> Further arguments
                            passed to the aggregate.  The return value of this function will be used
                            as the <strong>$context</strong> argument in the next call of the step or finalize
                            functions.
                            
                            <info>null</info> for the first row; on subsequent rows it will have the value that
                            was previously returned from the step function; you should use this to
                            maintain the aggregate state.
                            
                            The current row number.
                            
                            The first argument passed to the aggregate.
                            
                            Further arguments passed to the aggregate.
  <info>mixed</info>     <strong>$context</strong>        <info>null</info> for the first row; on subsequent rows it will have the value that
                            was previously returned from the step function; you should use this to
                            maintain the aggregate state.
  <info>int</info>       <strong>$rownumber</strong>      The current row number.
  <info>mixed</info>     <strong>$value</strong>          The first argument passed to the aggregate.
  <info>mixed</info>     <strong>$values</strong>         Further arguments passed to the aggregate.
  <info>callable</info>  <strong>$finalize_func</strong>  Callback function to aggregate the "stepped" data from each row.  Once
                            all the rows have been processed, this function will be called and it
                            should then take the data from the aggregation context and return the
                            result. This callback function should return a type understood by SQLite
                            (i.e. scalar type).
                            
                            This function need to be defined as: <info>mixed</info>fini<info>mixed</info><strong>$context</strong><info>int</info><strong>$rowcount</strong>
                            <strong>$context</strong> Holds the return value from the very last call to the step
                            function. <strong>$rowcount</strong> Holds the number of rows over which the aggregate
                            was performed.  The return value of this function will be used as the
                            return value for the aggregate.
                            
                            Holds the return value from the very last call to the step function.
                            
                            Holds the number of rows over which the aggregate was performed.
  <info>mixed</info>     <strong>$context</strong>        Holds the return value from the very last call to the step function.
  <info>int</info>       <strong>$rowcount</strong>       Holds the number of rows over which the aggregate was performed.
  <info>int</info>       <strong>$num_args</strong>       Hint to the SQLite parser if the callback function accepts a
                            predetermined number of arguments.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * <strong>sqlite_create_function()</strong>
   * <strong>sqlite_create_aggregate()</strong>


id: PDO::sqliteCreateCollation
type: function
doc:
<comment>Description:</comment>
  Registers a User Defined Function for use as a collating function in SQL statements
    
  
  Bu işlev
  DENEYSELDİR. Bu işlevin davranışı, ismi
  ve belgeleri PHP'nin sonraki sürümlerinde hiçbir duyuru yapılmaksızın
  değiştirilebilir. Bu risk göze alınamayacaksa bu işlev
  kullanılmamalıdır.

<comment>Param:</comment>
  <info>string</info>    <strong>$name</strong>      Name of the SQL collating function to be created or redefined.
  <info>callable</info>  <strong>$callback</strong>  The name of a PHP function or user-defined function to apply as a callback,
                       defining the behavior of the collation. It should accept two strings and
                       return as strcmp() does, i.e. it should return -1, 1, or 0 if the first
                       string sorts before, sorts after, or is equal to the second.
                       
                       This function need to be defined as: <info>int</info>collation<info>string</info><strong>$string1</strong><info>string</info><strong>$string2</strong>

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: PDO::sqliteCreateFunction
type: function
doc:
<comment>Description:</comment>
  Registers a User Defined Function for use in SQL statements
    
  
  Bu işlev
  DENEYSELDİR. Bu işlevin davranışı, ismi
  ve belgeleri PHP'nin sonraki sürümlerinde hiçbir duyuru yapılmaksızın
  değiştirilebilir. Bu risk göze alınamayacaksa bu işlev
  kullanılmamalıdır.
  
  This method allows you to register a PHP function with SQLite as an  UDF (User Defined Function),
  so that it can be called from within your SQL statements.
  
  The UDF can be used in any SQL statement that can call functions, such as SELECT and UPDATE
  statements and also in triggers.

<comment>Param:</comment>
  <info>string</info>    <strong>$function_name</strong>  The name of the function used in SQL statements.
  <info>callable</info>  <strong>$callback</strong>       Callback function to handle the defined SQL function.
                            
                            Callback functions should return a type understood by SQLite (i.e.
                            scalar type).
                            
                            This function need to be defined as:
                            <info>mixed</info>callback<info>mixed</info><strong>$value</strong><info>mixed</info><strong>$values</strong> <strong>$value</strong> The first argument passed to
                            the SQL function. <strong>$values</strong> Further arguments passed to the SQL function.
                            
                            The first argument passed to the SQL function.
                            
                            Further arguments passed to the SQL function.
  <info>mixed</info>     <strong>$value</strong>          The first argument passed to the SQL function.
  <info>mixed</info>     <strong>$values</strong>         Further arguments passed to the SQL function.
  <info>int</info>       <strong>$num_args</strong>       The number of arguments that the SQL function takes. If this parameter
                            is <return>-1</return>, then the SQL function may take any number of arguments.
  <info>int</info>       <strong>$flags</strong>          A bitwise conjunction of flags. Currently, only
                            <info>PDO::SQLITE_DETERMINISTIC</info> is supported, which specifies that the
                            function always returns the same result given the same inputs within a
                            single SQL statement.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * 
   * <strong>sqlite_create_function()</strong>
   * <strong>sqlite_create_aggregate()</strong>


id: PDOStatement
type: class
doc:
<comment>Description:</comment>
  Bir hazır deyimi ve hazır deyim çalıştırıldıktan sonra sonuç kümesini temsil eder.


id: PDOStatement::bindColumn
type: function
doc:
<comment>Description:</comment>
  Bir sütunu bir PHP değişkeni ile ilişkilendirir
    
  
  Bir sorgunun sonuç kümesindeki belli bir sütunu bir değişken ile ilişkilendirir. Her
  PDOStatement::fetch veya PDOStatement::fetchAll çağrısında sütunlarla ilişkili değişkenler
  güncellenir.
  
  Deyim çalıştırılana kadar sütun bilgisi PDO'ya görünür olmadığından taşınabilir uygulamaların bu
  yöntemi bir PDOStatement::execute çağrısından sonra kullanmaları gerekir.
  
  Ancak, PgSQL sürücüsü kullanılırken bir LOB sütununu bir akımla ilişkilendirmek için bu yöntemin
  PDOStatement::execute çağrısından önce kullanılması gerekir. Aksi takdirde büyük nesnenin nesne
  kimliği (oid) bir tamsayı olarak döner.

<comment>Param:</comment>
  <info>string|int</info>  <strong>$sütun</strong>      Sütunun numarası veya ismi; sütun numaraları 1'den başlar. Sütun isminin
                           sürücüden dönen isimle aynı harf büyüklüklerine sahip olmasına dikkat
                           edin.
  <info>mixed</info>       <strong>$değişken</strong>  Sütun ile ilişkilendirilecek PHP değişkeninin ismi.
  <info>int</info>         <strong>$veri_türü</strong>  <return>PDO::PARAM_*</return> sabitlerinden biri olarak veri türü.
  <info>int</info>         <strong>$uzunluk</strong>     Yer ayırmak için ipucu olarak kullanılır.
  <info>mixed</info>       <strong>$seçenekler</strong>  Sürücü için isteğe bağlı bağımsız değişkenler.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDOStatement::execute
   * PDOStatement::fetch
   * PDOStatement::fetchAll
   * PDOStatement::fetchColumn


id: PDOStatement::bindParam
type: function
doc:
<comment>Description:</comment>
  Bir bağımsız değişkeni belirtilen değişkenle ilişkilendirir
    
  
  Bir PHP değişkenini hazır SQL deyimindeki bir isimli veya soru imli bağımsız değişkenle
  ilişkilendirir. PDOStatement::bindValue yönteminin tersine değişken gönderimli olarak
  ilişkilendirilir ve sadece PDOStatement::execute çağrısı sırasında değerlendirmeye alınır.
  
  Bağımsız değişkenler çoğunlukla girdi bağımsız değişkenidir, yani bağımsız değişkenler sadece
  sorguda salt okunur olarak ele alınır (ancak yine de <strong>$veri_türü</strong>ne göre tür dönüşümü olabilir).
  Bazı sürücüler, veriyi çıktı bağımsız değişkenlerinde döndüren kayıtlı yordamların kullanımını
  mümkün kılar. Bazıları ise aynı bağımsız değişkenlerin hem girdi hem de çıktı için kullanımını
  mümkün kılar.

<comment>Param:</comment>
  <info>string|int</info>  <strong>$bağımsız_değişken</strong>  Bağımsız değişken betimleyicisi. İsimli bağımsız değişkenler için
                                  :isim biçemindedir. Soru imli bağımsız değişkenler için ise soru
                                  iminin konumudur. Konumlar 1'den başlar.
  <info>mixed</info>       <strong>$değişken</strong>         SQL deyimindeki bağımsız değişken ile ilişkilendirilecek PHP
                                  değişkeni.
  <info>int</info>         <strong>$veri_türü</strong>        <return>PDO::PARAM_*</return> sabitlerinden biri olarak veri türü. Bağımsız
                                  değişkenden değer de döndürmek istiyorsanız
                                  <info>PDO::PARAM_INPUT_OUTPUT</info> sabitini burada, bit seviyesinde
                                  VEYAlayın.
  <info>int</info>         <strong>$uzunluk</strong>            Veri türünün uzunluğu. Bağımsız değişken çıktı almak amacıyla
                                  kullanılacaksa veri türü uzunluğu mutlaka belirtilmelidir. Sadece
                                  <strong>$veri_türü</strong> bağımsız değişkeninde <info>PDO::PARAM_INPUT_OUTPUT</info>
                                  belirtilmişse anlamlıdır.
  <info>mixed</info>       <strong>$seçenekler</strong>        Sürücü seçenekleri.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::execute
   * PDOStatement::bindValue


id: PDOStatement::bindValue
type: function
doc:
<comment>Description:</comment>
  Bir değeri bir bağımsız değişken ile ilişkilendirir
    
  
  Hazır SQL deyimindeki bir isimli veya soru imli bağımsız değişkenle bir değeri ilişkilendirir.

<comment>Param:</comment>
  <info>string|int</info>  <strong>$bağımsız_değişken</strong>  Bağımsız değişken betimleyicisi. İsimli bağımsız değişkenler için
                                  :isim biçemindedir. Soru imli bağımsız değişkenler için ise soru
                                  iminin konumudur. Konumlar 1'den başlar.
  <info>mixed</info>       <strong>$değer</strong>             Bağımsız değişken ile ilişkilendirilecek değer.
  <info>int</info>         <strong>$veri_türü</strong>        <return>PDO::PARAM_*</return> sabitlerinden biri olarak veri türü.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::execute
   * PDOStatement::bindParam


id: PDOStatement::closeCursor
type: function
doc:
<comment>Description:</comment>
  Göstericiyi kapatarak deyimin tekrar çalıştırılabilmesini sağlar
    
  
  PDOStatement::closeCursor yöntemi sunucu bağlantısını serbest bırakarak, mevcut deyimin durumunu
  değiştirmeden tekrar çalıştırılabilmesinin yanında başka SQL deyimlerinin çalıştırılabilmesini de
  mümkün kılar.
  
  Evvelce çalıştırılmış bir PDOStatement nesnesinden henüz alınmamış satırların olduğu durumda bazı
  sürücüler bir PDOStatement nesnesinin daha çalıştırılmasına izin vermezler. Bu yöntem bu tür
  sürücülerde yararlıdır. Sürücünüz böyle bir sürücü ise sorun sıra dışı bir hata olarak kendini
  gösterir.
  
  PDOStatement::closeCursor yöntemi ya sürücüye özel isteğe bağlı (azami verimlilikte) bir yöntemdir
  ya da genel amaçlı bir PDO son çare yöntemidir. Genel amaçlı yöntem aşağıdaki PHP koduna eşdeğer
  bir işlem yürütür: fetch()) ; if (!$stmt->nextRowset()) break;
  } while (true);
  ?>
  ]]>

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDOStatement::execute


id: PDOStatement::columnCount
type: function
doc:
<comment>Description:</comment>
  Sonuç kümesindeki sütun sayısını döndürür
    
  
  PDOStatement nesnesi ile temsil edilen sonuç kümesindeki sütun sayısını döndürür.
  
  Eğer PDOStatement nesnesi PDO::query yönteminden dönmüşse sütun sayısı hemen alınabilir.
  
  Eğer PDOStatement nesnesi PDO::prepare yönteminden dönmüşse sütun sayısı ancak
  PDOStatement::execute çağrısından sonra alınabilir.

<comment>Return:</comment>
  <info>int</info>  Sonuç kümesi boş olsa bile, sütun sayısı bir tamsayı olarak döner. Bir sonuç kümesi yoksa
       işlev <return>0</return> döndürür.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::execute
   * PDOStatement::rowCount


id: PDOStatement::debugDumpParams
type: function
doc:
<comment>Description:</comment>
  Bir SQL hazır komutunu dökümler
  
  Bir hazır deyimin içerdiği bilgiyi doğrudan çıktıya dökümler. Bu bilgi, kullanımdaki SQL sorgusu
  (<return>SQL</return>), anahtar adı veya konumlarıyla birlikte bağımsız değişkenlerin listesini, adlarını,
  sorgudaki konumlarını (PDO sürücü destekliyorsa; yoksa -1'dir) tamsayı olarak türünü (<return>param_type</return>)
  ve <return>is_param</return> mantıksal değerini içerir.
  
  Bu işlev, veriyi doğrudan çıktıya basan bir hata ayıklama işlevidir. Sonuçlarını doğrudan
  tarayıcıya
  çıktılayan her şey gibi, çıktı denetleme
  işlevleri bu işlevin de çıktısını yakalamak ve (örneğin)
  <info>string</info> türünde saklamak için kullanılabilir.
  
  Sonuçlarını doğrudan tarayıcıya
  çıktılayan her şey gibi, çıktı denetleme
  işlevleri bu işlevin de çıktısını yakalamak ve (örneğin)
  <info>string</info> türünde saklamak için kullanılabilir.
  
  İşlev, sadece deyim içindeki bağımsız değişkenleri dökümler. Ek bağımsız değişkenler deyimde
  saklanmaz ve gösterilmez.

<comment>Return:</comment>
  <info>bool|null</info>  Başarı durumunda <info>null</info>, hata durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::bindParam
   * PDOStatement::bindValue


id: PDOStatement::errorCode
type: function
doc:
<comment>Description:</comment>
  Deyim üzerindeki son işlemle ilgili SQLSTATE hata kodunu döndürür

<comment>Return:</comment>
  <info>string|null</info>  Sadece deyim üzerindeki son işlemle ilgili SQLSTATE hata kodunu döndürmesi dışında
               PDO::errorCode yöntemiyle aynıdır.

<comment>See Also:</comment>
   * PDO::errorCode
   * PDO::errorInfo
   * PDOStatement::errorInfo


id: PDOStatement::errorInfo
type: function
doc:
<comment>Description:</comment>
  Deyim üzerindeki son işlemle ilgili hata bilgisini döndürür

<comment>Return:</comment>
  <info>array</info>  Deyim üzerindeki son işlemle ilgili hata bilgisini bir dizi olarak döndürür. Dizi en
         azından şu alanları içerir: ElemanBilgi0SQLSTATE hata kodu (ANSI SQL standardında tanımlı 5
         abecesayısal karakterli bir betimleyici).1Sürücüye özgü hata kodu.2Sürücüye özgü hata
         iletisi.

<comment>See Also:</comment>
   * PDO::errorCode
   * PDO::errorInfo
   * PDOStatement::errorCode


id: PDOStatement::execute
type: function
doc:
<comment>Description:</comment>
  Bir hazır deyimi çalıştırır
  
  Bir hazır deyimi çalıştırır. Hazır deyim bağımsız değişken içeriyorsa şu ikisinden birini
  yapmalısınız:  Bağımsız değişkenleri ve/veya değerleri soru imleri ile ilişkilendirmek için
  (sırasıyla)  PDOStatement::bindParam ve/veya PDOStatement::bindValue yöntemi kullanılmalıdır.
  İlişkili değişkenler, değerlerini girdi olarak iletir ve varsa çıktı değerlerini  ya da aktarılan
  salt-girdi bağımsız değişken değerlerini bir dizi olarak alır.
  
  Bağımsız değişkenleri ve/veya değerleri soru imleri ile ilişkilendirmek için (sırasıyla)
  PDOStatement::bindParam ve/veya PDOStatement::bindValue yöntemi kullanılmalıdır. İlişkili
  değişkenler, değerlerini girdi olarak iletir ve varsa çıktı değerlerini
  
  ya da aktarılan salt-girdi bağımsız değişken değerlerini bir dizi olarak alır.

<comment>Param:</comment>
  <info>array|null</info>  <strong>$girdiler</strong>  Çalıştırılacak SQL deyimiyle ilişkilendirilmiş bağımsız değişken sayısı
                         kadar değer içeren bir dizi. Tüm değerler <info>PDO::PARAM_STR</info> olarak ele alınır.
                         
                         Tek bir bağımsız değişkene birden fazla değer belirtilemez. Örneğin bir
                         IN() yan tümcesindeki tek bir isimli bağımsız değişken iki değerle
                         ilişkilendirilemez.
                         
                         Belirtilenden daha fazla değeri ilişkilendirmek mümkün değildir; <strong>$girdiler</strong>
                         içinde PDO::prepare yönteminde belirtilen deyimdekinden daha fazla anahtar
                         mevcutsa, deyim başarısız olur ve bir hata çıktılanır.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::bindParam
   * PDOStatement::fetch
   * PDOStatement::fetchAll
   * PDOStatement::fetchColumn


id: PDOStatement::fetch
type: function
doc:
<comment>Description:</comment>
  Sonuç kümesindeki sonraki satırı döndürür
  
  PDOStatement nesnesi ile ilişkili sonuç kümesinden bir sonraki satırı döndürür. <strong>$kip</strong> bağımsız
  değişkeni ile PDO'nun satırı nasıl döndüreceği belirtilir.

<comment>Param:</comment>
  <info>int</info>  <strong>$kip</strong>              Sonrakı satırın nasıl döndürüleceğini belirtmek için kullanılır.
                         <return>PDO::FETCH_*</return> sabitlerinden biri olmalıdır. <info>PDO::FETCH_DEFAULT</info> öntanımlı
                         değerdir. <info>PDO::FETCH_ASSOC</info>: Sütun isimlerine indisli bir dizi döner.
                         <info>PDO::FETCH_BOTH</info> (öntanımlı): Hem sütun isimlerine hem de sütun numaralarına
                         göre indislenmiş bir dizi döner. İlk sütunun indisi 0'dır.
                         <info>PDO::FETCH_BOUND</info>: Sütun değerlerini PDOStatement::bindColumn ile
                         ilişkilendirilmiş PHP değişkenlerine atar ve <info>true</info> döndürür.
                         <info>PDO::FETCH_CLASS</info>: İstenen sınıfın özelliklerini sütun isimlerine eşleyerek
                         sınıfın bir örneğini döndürür ve <return>PDO::FETCH_PROPS_LATE</return> ayrıca
                         belirtilmemişse ardından kurucu çağrılır. Eğer <strong>$kip</strong> bağımsız değişkeni
                         <info>PDO::FETCH_CLASSTYPE</info> sabitini içeriyorsa (örn, <return>PDO::FETCH_CLASS |
                         PDO::FETCH_CLASSTYPE</return>) sınıf ismi ilk sütunun değerine göre belirlenir.
                         <info>PDO::FETCH_INTO</info>: İstenen sınıfın mevcut örneğini sütun isimlerini sınıf
                         özelliklerine eşleyerek günceller. <info>PDO::FETCH_LAZY</info>: <info>PDO::FETCH_BOTH</info> ve
                         <info>PDO::FETCH_OBJ</info> sabitlerinin birleşimidir. <info>PDO::FETCH_NAMED</info>: Aynı isimde
                         birden fazla sütun olmaması şartıyla <info>PDO::FETCH_ASSOC</info> sabitindeki gibi bir
                         dizi döndürür. Bir anahtar tarafından atıfta bulunulan değer, anahtarla
                         aynı isimli sütundaki tüm değerlerin dizisini içerecektir. <info>PDO::FETCH_NUM</info>:
                         Sütun numaralarına göre indislenmiş bir dizi döner. İlk sütunun indisi
                         0'dır. <info>PDO::FETCH_OBJ</info>: Özellik isimlerinin sınıf isimlerine denk düştüğü
                         bir anonim nesne örneği döndürür. <info>PDO::FETCH_PROPS_LATE</info>: <info>PDO::FETCH_CLASS</info>
                         ile birlikte kullanıldığında, özellikler ilgili sütundaki değerlere
                         atanmadan önce sınıf kurucusu çağrılır.
                         
                         <info>PDO::FETCH_ASSOC</info>: Sütun isimlerine indisli bir dizi döner.
                         
                         <info>PDO::FETCH_BOTH</info> (öntanımlı): Hem sütun isimlerine hem de sütun numaralarına
                         göre indislenmiş bir dizi döner. İlk sütunun indisi 0'dır.
                         
                         <info>PDO::FETCH_BOUND</info>: Sütun değerlerini PDOStatement::bindColumn ile
                         ilişkilendirilmiş PHP değişkenlerine atar ve <info>true</info> döndürür.
                         
                         <info>PDO::FETCH_CLASS</info>: İstenen sınıfın özelliklerini sütun isimlerine eşleyerek
                         sınıfın bir örneğini döndürür ve <return>PDO::FETCH_PROPS_LATE</return> ayrıca
                         belirtilmemişse ardından kurucu çağrılır. Eğer <strong>$kip</strong> bağımsız değişkeni
                         <info>PDO::FETCH_CLASSTYPE</info> sabitini içeriyorsa (örn, <return>PDO::FETCH_CLASS |
                         PDO::FETCH_CLASSTYPE</return>) sınıf ismi ilk sütunun değerine göre belirlenir.
                         
                         <info>PDO::FETCH_INTO</info>: İstenen sınıfın mevcut örneğini sütun isimlerini sınıf
                         özelliklerine eşleyerek günceller.
                         
                         <info>PDO::FETCH_LAZY</info>: <info>PDO::FETCH_BOTH</info> ve <info>PDO::FETCH_OBJ</info> sabitlerinin
                         birleşimidir.
                         
                         <info>PDO::FETCH_NAMED</info>: Aynı isimde birden fazla sütun olmaması şartıyla
                         <info>PDO::FETCH_ASSOC</info> sabitindeki gibi bir dizi döndürür. Bir anahtar tarafından
                         atıfta bulunulan değer, anahtarla aynı isimli sütundaki tüm değerlerin
                         dizisini içerecektir.
                         
                         <info>PDO::FETCH_NUM</info>: Sütun numaralarına göre indislenmiş bir dizi döner. İlk
                         sütunun indisi 0'dır.
                         
                         <info>PDO::FETCH_OBJ</info>: Özellik isimlerinin sınıf isimlerine denk düştüğü bir
                         anonim nesne örneği döndürür.
                         
                         <info>PDO::FETCH_PROPS_LATE</info>: <info>PDO::FETCH_CLASS</info> ile birlikte kullanıldığında,
                         özellikler ilgili sütundaki değerlere atanmadan önce sınıf kurucusu
                         çağrılır.
  <info>int</info>  <strong>$göst_yönü</strong>     Kaydırılabilir göstericili bir PDOStatement nesnesi için, bu değer hangi
                         satırın döndürüleceğini belirler. <return>PDO::FETCH_ORI_*</return> sabitlerinden biri
                         olmalıdır. <info>PDO::FETCH_ORI_NEXT</info> öntanımlı değerdir. PDOStatement nesnenize
                         bir kaydırılabilir gösterici isteği yapmak için SQL deyimini PDO::prepare
                         ile hazırlarken <info>PDO::CURSOR_SCROLL</info> özelliğine <info>PDO::ATTR_CURSOR</info> özniteliğini
                         atamalısınız.
  <info>int</info>  <strong>$göst_başlangıcı</strong>  Kaydırılabilir göstericili bir PDOStatement nesnesi için <strong>$göst_yönü</strong>
                         bağımsız değişkeninde <info>PDO::FETCH_ORI_ABS</info> belirtilirse bu değer sonuç
                         kümesinden alınacak mutlak satır numarasını belirler.
                         
                         Kaydırılabilir göstericili bir PDOStatement nesnesi için <strong>$göst_yönü</strong>
                         bağımsız değişkeninde <info>PDO::FETCH_ORI_REL</info> belirtilirse bu değer alınacak
                         satırı bir önceki PDOStatement::fetch çağrısındaki gösterici konumuna
                         göreli olarak belirler.

<comment>Return:</comment>
  <info>mixed</info>  Bu işlevin dönüş değeri alım türüne bağlıdır. Başarısızlık durumunda veya döndürülecek
         satır kalmamışsa <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::prepare
   * PDOStatement::execute
   * PDOStatement::fetchAll
   * PDOStatement::fetchColumn
   * PDOStatement::fetchObject
   * PDOStatement::setFetchMode


id: PDOStatement::fetchAll
type: function
doc:
<comment>Description:</comment>
  Sonuç kümesinde kalan satırları döndürür

<comment>Param:</comment>
  <info>int</info>         <strong>$kip</strong>                   PDOStatement::fetch yönteminde açıklandığı gibi döndürülen
                                     dizinin içeriğini belirleyen sabit. <info>PDO::FETCH_DEFAULT</info>
                                     öntanımlıdır.
                                     
                                     Sonuç kümesindeki tek bir sütunun tüm değerleri içeren bir dizi
                                     döndürmek için <info>PDO::FETCH_COLUMN</info> belirtin. Bu durumda hangi
                                     sütunun içeriğinin alınacağını <strong>$sütun</strong> ile belirtin.
                                     
                                     Sonuç kümesindeki tek bir sütunun eşsiz değerleri içeren bir
                                     dizi döndürmek için <info>PDO::FETCH_COLUMN</info> ile <info>PDO::FETCH_UNIQUE</info>
                                     sabitini bit seviyesinde VEYAlayın.
                                     
                                     Belirtilen sütunun değerlerine göre gruplanmış bir ilişkisel
                                     dizi döndürmek için <info>PDO::FETCH_COLUMN</info> ile <info>PDO::FETCH_GROUP</info>
                                     sabitini bit seviyesinde VEYAlayın.
  <info>int</info>         <strong>$sütun</strong>                <info>PDO::FETCH_COLUMN</info> ile kullanılır. İlk sütunun indisinin <return>0</return>
                                     olduğu varsayımıyla sütun indisi.
  <info>array|null</info>  <strong>$bağımsız_değişkenler</strong>  <info>PDO::FETCH_CLASS</info> ile kullanılır. Belirtilen sınıfın örnekleri,
                                     her sütun sınıfın isimli özellikleriyle eşleştirilerek
                                     döndürülür.
  <info>callable</info>    <strong>$geriçağırım</strong>       <info>PDO::FETCH_FUNC</info> ile kullanılır. Belirtilen işlevin sonuçları,
                                     her satırın sütunları çağrıda bağımsız değişken olarak
                                     kullanılarak döndürülür.

<comment>Return:</comment>
  <info>array</info>  Sonuç kümesinde kalan satırların tümünü bir dizi olarak döndürür. Dizinin her elemanı birer
         satır içerir ve bu satır elemanları sütun değerlerini içeren bir dizi ya da sütun
         isimlerinin özelliklere karşı düştüğü bir nesne içerir. Sıfır sonuç için boş dizi döner.
         
         Büyük sonuç kümelerini almak için bu yöntemi kullanmak sistem ve muhtemelen ağ
         kaynaklarından aşırı taleplere yol açar. Tüm veriyi alıp PHP ile işleme tabi tutmak yerine
         sonuç kümeleri üzerinde işlem yapmak için veritabanı sunucusunu kullanmak daha iyi
         olabilir. Örneğin, SQL'de WHERE ve ORDER BY yan tümcelerini kullanarak, PHP'de işleme
         sokmadan önce sonuç kümesini küçültebilirsiniz.

<comment>See Also:</comment>
   * PDO::query
   * PDOStatement::fetch
   * PDOStatement::fetchColumn
   * PDO::prepare
   * PDOStatement::setFetchMode


id: PDOStatement::fetchColumn
type: function
doc:
<comment>Description:</comment>
  Sonuç kümesindeki sonraki satırdan tek bir sütun döndürür
    
  
  Sonuç kümesindeki sonraki satırdan tek bir sütun döndürür; artık satır kalmamışsa <info>false</info> döner.
  
  PDOStatement::fetchColumn mantıksal sütunların alımında kullanılmamalıdır, çünkü sütundaki bir
  <info>false</info> değerini alınacak satır kalmadığında dönen <info>false</info> değerinden ayırmak imkansızdır. Böyle bir
  durumda PDOStatement::fetch kullanılmalıdır.

<comment>Param:</comment>
  <info></info>  <strong>$sütunnum</strong>  Sütunun numarası. İlk sütunun indisi 0'dır. Bağımsız değişkende hiçbir değer
               belirtilmemişse ilk sütunun değeri döner.

<comment>Return:</comment>
  <info>mixed</info>  Sonuç kümesinde sonraki satırdan tek bir sütunun değerini bir dizge olarak döndürür.
         Satırlar tükenince <info>false</info> döner.
         
         Veriyi almak için PDOStatement::fetchColumn yöntemini kullanırsanız aynı satırdan artık
         başka bir sütun döndüremezsiniz.

<comment>See Also:</comment>
   * PDO::query
   * PDOStatement::fetch
   * PDOStatement::fetchAll
   * PDO::prepare
   * PDOStatement::setFetchMode


id: PDOStatement::fetchObject
type: function
doc:
<comment>Description:</comment>
  Sonraki satırı alır ve bir nesne olarak döndürür
  
  Sonraki satırı bir nesne olarak döndürür. Bu yöntem PDOStatement::fetch yönteminin
  <info>PDO::FETCH_CLASS</info> veya <info>PDO::FETCH_OBJ</info> kipinde kullanımına denktir.
  
  Bir satır alındığında, sınıfın özelliklerine ilgili sütunun değerleri atanır ve ardından sınıf
  kurucusu çağrılır.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$sınıf</strong>               Oluşturulan sınıfın ismi; <return>stdClass</return> öntanımlıdır.
  <info>array</info>        <strong>$bağımsız_değişkenler</strong>  Bu dizinin elemanları kurucuya bağımsız değişken olarak
                                      aktarılır.

<comment>Return:</comment>
  <info>object|false</info>  Sütun isimlerinin özellik isimlerine denk düştüğü sınıfın bir örneğini döndürür.
                İşlem sırasında bir hata oluşursa <info>false</info> döner.

<comment>See Also:</comment>
   * PDOStatement::fetch


id: PDOStatement::getAttribute
type: function
doc:
<comment>Description:</comment>
  Bir deyim özniteliğini döndürür
  
  Bir deyim özniteliğinin değerini döndürür. Henüz tek bir sürücüye özel özniteliğin dışında
  öznitelik yoktur: <return>PDO::ATTR_CURSOR_NAME</return> (Firebird ve ODBC'ye özgüdür): <return>UPDATE ... WHERE CURRENT OF</return>
  için gösterici ismini içerir.  Sürücüye özgü özniteliklerin başka sürücülerde kullanılmamasına ise
  özellikle dikkat edilmelidir.
  
  <return>PDO::ATTR_CURSOR_NAME</return> (Firebird ve ODBC'ye özgüdür): <return>UPDATE ... WHERE CURRENT OF</return> için gösterici
  ismini içerir.

<comment>Param:</comment>
  <info>int</info>  <strong>$isim</strong>  Sorgulanan özniteliğin ismi.

<comment>Return:</comment>
  <info>mixed</info>  Özniteliğin değeri.

<comment>See Also:</comment>
   * PDO::getAttribute
   * PDO::setAttribute
   * PDOStatement::setAttribute


id: PDOStatement::getColumnMeta
type: function
doc:
<comment>Description:</comment>
  Sonuç kümesindeki bir sütunla ilgili temel veriyi döndürür
    
  
  Sütun numarası belirtilen sütunla ilgili temel verileri içeren bir ilişkisel dizi döndürür.
  
  PDOStatement::getColumnMeta yöntemini seçimlik olarak bazı veritabanı sürücüleri desteklemez.
  Ancak bu kılavuzda belgelenen tüm PDO sürücüleri bu işlevi gerçekler.

<comment>Param:</comment>
  <info>int</info>  <strong>$sütun</strong>  Sütun numarası; ilk sütunun numarası 0'dır.

<comment>Return:</comment>
  <info>array|false</info>  Aşağıdaki alanlara sahip bir ilişkisel dizi döner:
               
               İstenen sütun sonuç kümesinde yoksa veya hiç sonuç kümesi yoksa <info>false</info> döner.

<comment>See Also:</comment>
   * PDOStatement::columnCount
   * PDOStatement::rowCount


id: PDOStatement::getIterator
type: function
doc:
<comment>Description:</comment>
  Gets result set iterator
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>Iterator</info>  


id: PDOStatement::nextRowset
type: function
doc:
<comment>Description:</comment>
  Çok satır kümeli bir sonuçtaki sonraki satır kümesini geçerli satır kümesi yapar
  
  Bazı veritabanları birden fazla satır kümesi (sonuç kümesi diye de bilinir) döndüren kayıtlı
  yordamları destekler. PDOStatement::nextRowset yordamını kullaranak bir PDOStatement nesnesi ile
  ilişkili satır kümelerinin ikincisine ve sırayla sonraki satır kümelerine erişebilirsiniz. Her
  satır kümesi diğerlerinden farklı sütunlardan oluşabilir.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDOStatement::columnCount
   * PDOStatement::execute
   * PDOStatement::getColumnMeta
   * PDO::query


id: PDOStatement::rowCount
type: function
doc:
<comment>Description:</comment>
  Son SQL deyiminden etkilenen satır sayısını döndürür
    
  
  <return>PDOStatement</return> nesnesi tarafından çalıştırılan son DELETE, INSERT veya UPDATE deyiminden etkilenen
  satır sayısını döndürür.
  
  <return>SELECT</return> gibi sonuç kümeleri oluşturan deyimler için davranış belirsizdir ve her sürücü için
  farklıdır. Bazı veritabanları (örneğin, MySQL tamponlu kipteyken) bu deyim tarafından üretilen
  satır sayısını döndürebilmektedir. Ancak bu davranış tüm veritabanları için garanti edilmediğinden
  taşınıbilir bir uygulamada bu davranışa itibar edilmemelidir.
  
  Bu yöntem SQLite sürücü ile ve <info>PDO::CURSOR_SCROLL</info> özniteliğine <info>PDO::ATTR_CURSOR</info> atandığında
  PostgreSQL sürücüsü ile daima "0" (sıfır) döndürür.

<comment>Return:</comment>
  <info>int</info>  Etkilenen satır sayısı.

<comment>See Also:</comment>
   * PDOStatement::columnCount
   * PDOStatement::fetchColumn
   * PDO::query


id: PDOStatement::setAttribute
type: function
doc:
<comment>Description:</comment>
  Bir deyim özniteliğini tanımlar
  
  Belirtilen deyim özniteliğine bir değer atar. Şimdilik genele yönelik hiç öznitelik yoktur.
  Sürücüye özel tek bir öznitelik vardır: <return>PDO::ATTR_CURSOR_NAME</return> (Firebird ve ODBC'ye özel): <return>UPDATE
  ... WHERE CURRENT OF</return> deyimi için gösterici ismini belirler.  Sürücüye özgü özniteliklerin başka
  sürücülerde kullanılmamasına ise özellikle dikkat edilmelidir.
  
  <return>PDO::ATTR_CURSOR_NAME</return> (Firebird ve ODBC'ye özel): <return>UPDATE ... WHERE CURRENT OF</return> deyimi için
  gösterici ismini belirler.

<comment>Param:</comment>
  <info>int</info>    <strong>$öznitelik</strong>  Tanımlanacak öznitelik.
  <info>mixed</info>  <strong>$değer</strong>     <strong>$öznitelik</strong> için atanacak değer; özniteliğe bağlı olarak belirli bir tür
                     gerekebilir.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * PDO::getAttribute
   * PDO::setAttribute
   * PDOStatement::getAttribute


id: PDOStatement::setFetchMode
type: function
doc:
<comment>Description:</comment>
  Deyim için öntanımlı veri alım kipini belirler

<comment>Param:</comment>
  <info>int</info>         <strong>$kip</strong>                   <return>PDO::FETCH_*</return> sabitlerinden biri olarak veri alım kipi.
  <info>int</info>         <strong>$sütunnum</strong>             Sütun numarası.
  <info>string</info>      <strong>$sınıfadı</strong>           Sınıf adı.
  <info>array|null</info>  <strong>$bağımsız_değişkenler</strong>  Kurucu bağımsız değişkenleri.
  <info>object</info>      <strong>$nesne</strong>                 Nesne.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: PGSQL_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return an associative array of field names and values.


id: PGSQL_BAD_RESPONSE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. The server's response  was not understood.


id: PGSQL_BOTH
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return an array of field values that is both numerically indexed (by
  field number) and associated (by field name).


id: PGSQL_COMMAND_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Successful completion of a  command returning no data.


id: PGSQL_CONNECTION_BAD
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connection_status()</strong> indicating that the database connection is in an invalid state.


id: PGSQL_CONNECTION_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connection_status()</strong> indicating that the database connection is in a valid state.


id: PGSQL_CONNECT_ASYNC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_connect()</strong> to create an asynchronous connection.


id: PGSQL_CONNECT_FORCE_NEW
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_connect()</strong> to force the creation of a new connection, rather than re-using an existing
  identical connection.


id: PGSQL_CONV_FORCE_NULL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Use SQL <return>NULL</return> in place of an empty <info>string</info>.


id: PGSQL_CONV_IGNORE_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Ignore default values in the table during conversion.


id: PGSQL_CONV_IGNORE_NOT_NULL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Ignore conversion of <info>null</info> into SQL <return>NOT NULL</return> columns.


id: PGSQL_COPY_IN
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Copy In (to server) data  transfer started.


id: PGSQL_COPY_OUT
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Copy Out (from server) data  transfer started.


id: PGSQL_DIAG_CONTEXT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. An indication of the context in which the error occurred.
  Presently  this includes a call stack traceback of active procedural language  functions and
  internally-generated queries. The trace is one entry  per line, most recent first.


id: PGSQL_DIAG_INTERNAL_POSITION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. This is defined the same as the <info>PG_DIAG_STATEMENT_POSITION</info>
  field, but  it is used when the cursor position refers to an internally generated  command rather
  than the one submitted by the client. The  <info>PG_DIAG_INTERNAL_QUERY</info> field will always appear when
  this  field appears.


id: PGSQL_DIAG_INTERNAL_QUERY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The text of a failed internally-generated command. This could
  be, for example, a  SQL query issued by a PL/pgSQL function.


id: PGSQL_DIAG_MESSAGE_DETAIL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. Detail: an optional secondary error message carrying more
  detail about the problem. May run to multiple lines.


id: PGSQL_DIAG_MESSAGE_HINT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. Hint: an optional suggestion what to do about the problem. This
  is intended to differ from detail in that it offers advice (potentially inappropriate) rather than
  hard facts. May run to multiple lines.


id: PGSQL_DIAG_MESSAGE_PRIMARY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The primary human-readable error message (typically one line).
  Always present.


id: PGSQL_DIAG_SEVERITY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The severity; the field contents are <return>ERROR</return>,  <return>FATAL</return>, or <return>PANIC</return>
  (in an error message), or  <return>WARNING</return>, <return>NOTICE</return>, <return>DEBUG</return>,  <return>INFO</return>, or <return>LOG</return> (in a notice message), or a
  localized  translation of one of these. Always present.


id: PGSQL_DIAG_SEVERITY_NONLOCALIZED
type: constant
doc:
<comment>Description:</comment>
  The severity; the field contents are ERROR, FATAL, or PANIC (in an error message), or WARNING,
  NOTICE, DEBUG, INFO, or LOG (in a notice message). This is identical to the PG_DIAG_SEVERITY field
  except that the contents are never localized. This is present only in versions 9.6 and later / PHP
  7.3.0 and later.


id: PGSQL_DIAG_SOURCE_FILE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The file name of the PostgreSQL source-code location where the
  error  was reported.


id: PGSQL_DIAG_SOURCE_FUNCTION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The name of the PostgreSQL source-code function reporting the
  error.


id: PGSQL_DIAG_SOURCE_LINE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The line number of the PostgreSQL source-code location where
  the  error was reported.


id: PGSQL_DIAG_SQLSTATE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The SQLSTATE code for the error. The SQLSTATE code identifies
  the type of error  that has occurred; it can be used by front-end applications to perform specific
  operations (such as error handling) in response to a particular database error.  This field is not
  localizable, and is always present.


id: PGSQL_DIAG_STATEMENT_POSITION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. A string containing a decimal integer indicating an error
  cursor position as an index into the original  statement string. The first character has index 1,
  and positions are measured in characters not bytes.


id: PGSQL_DML_ASYNC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Execute asynchronous query by
  these functions.


id: PGSQL_DML_ESCAPE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Apply escape to all parameters
  instead of calling <strong>pg_convert()</strong> internally. This option omits meta data look up. Query could be as
  fast as <strong>pg_query()</strong> and <strong>pg_send_query()</strong>.


id: PGSQL_DML_EXEC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Execute query by these functions.


id: PGSQL_DML_NO_CONV
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. All parameters passed as is.
  Manual escape is required if parameters contain user supplied data. Use <strong>pg_escape_string()</strong> for it.


id: PGSQL_DML_STRING
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Return executed query string.


id: PGSQL_EMPTY_QUERY
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. The string sent to the server was empty.


id: PGSQL_ERRORS_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. The default mode produces messages that include the above
  plus any detail, hint, or context fields (these may span  multiple lines).


id: PGSQL_ERRORS_TERSE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. Specified that returned messages include severity, primary
  text,  and position only; this will normally fit on a single line.


id: PGSQL_ERRORS_VERBOSE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. The verbose mode includes all available fields.


id: PGSQL_FATAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. A fatal error  occurred.


id: PGSQL_LIBPQ_VERSION_STR
type: constant
doc:
<comment>Description:</comment>
  Prior to PHP 8.0.0, the long libpq version that includes compiler information. As of PHP 8.0.0,
  the value is identical to <info>PGSQL_LIBPQ_VERSION</info>, and using <info>PGSQL_LIBPQ_VERSION_STR</info> is deprecated.


id: PGSQL_NONFATAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. A nonfatal error  (a notice or warning) occurred.


id: PGSQL_NOTICE_ALL
type: constant
doc:
<comment>Description:</comment>
  Used by <strong>pg_last_notice()</strong>. Available since PHP 7.1.0.


id: PGSQL_NUM
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return a numerically indexed array of field numbers and values.


id: PGSQL_POLLING_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is currently active.


id: PGSQL_POLLING_FAILED
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection attempt failed.


id: PGSQL_POLLING_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is ready to be used.


id: PGSQL_POLLING_READING
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is waiting for the PostgreSQL socket
  to be readable.


id: PGSQL_POLLING_WRITING
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is waiting for the PostgreSQL socket
  to be writable.


id: PGSQL_SEEK_CUR
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the current position.


id: PGSQL_SEEK_END
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the end of the object.


id: PGSQL_SEEK_SET
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the start of the object.


id: PGSQL_SHOW_CONTEXT_ALWAYS
type: constant
doc:
<comment>Description:</comment>
  To be used with <strong>pg_set_error_context_set_visibility()</strong>, the context's fieds are included in error,
  notice and warning messages. Available as of PHP 8.3.0.


id: PGSQL_SHOW_CONTEXT_ERRORS
type: constant
doc:
<comment>Description:</comment>
  To be used with <strong>pg_set_error_context_set_visibility()</strong>, the context's fieds are included in error
  messages only. This is the default behaviour. Available as of PHP 8.3.0.


id: PGSQL_SHOW_CONTEXT_NEVER
type: constant
doc:
<comment>Description:</comment>
  To be used with <strong>pg_set_error_context_set_visibility()</strong>, the context is never shown. Available as of
  PHP 8.3.0.


id: PGSQL_STATUS_LONG
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_status()</strong>.  Indicates that numerical result code is desired.


id: PGSQL_STATUS_STRING
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_status()</strong>.  Indicates that textual result command tag is desired.


id: PGSQL_TRACE_REGRESS_MODE
type: constant
doc:
<comment>Description:</comment>
  To be used with <strong>pg_trace()</strong>, fields such as OIDs are included in the trace's messages. Available as
  of PHP 8.3.0.


id: PGSQL_TRACE_SUPPRESS_TIMESTAMPS
type: constant
doc:
<comment>Description:</comment>
  To be used with <strong>pg_trace()</strong>, the timestamp is not included in the trace's messages. Available as of
  PHP 8.3.0.


id: PGSQL_TRANSACTION_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. A command is in progress on the connection.  A query has been
  sent via the connection and not yet completed.


id: PGSQL_TRANSACTION_IDLE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. Connection is currently idle, not in a transaction.


id: PGSQL_TRANSACTION_INERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is idle, in a failed transaction block.


id: PGSQL_TRANSACTION_INTRANS
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is idle, in a transaction block.


id: PGSQL_TRANSACTION_UNKNOWN
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is bad.


id: PGSQL_TUPLES_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Successful completion of a command  returning data (such as a
  <return>SELECT</return> or <return>SHOW</return>).


id: PHP_BINARY
type: constant
doc:
<comment>Description:</comment>
  Betiklerin icrası için kullanılan çalıştılabilirin bulunduğu yer.


id: PHP_BINDIR
type: constant
doc:
<comment>Description:</comment>
  Yapılandırma sırasında atanan --bindir değeri. Windows'ta bu değer yapılandırma sırasında
  --with-prefix ile atanır.


id: PHP_EXTENSION_DIR
type: constant
doc:
<comment>Description:</comment>
  Yüklenebilir eklentilerin aranacağı öntanımlı dizin (extension_dir) ile geçersiz kılınmadığı
  takdirde). <info>PHP_PREFIX</info> (veya Windows üzerinde PHP_PREFIX . "\\ext") öntanımlıdır.


id: PHP_EXTRA_VERSION
type: constant
doc:
<comment>Description:</comment>
  Bir dizge olarak geçerli PHP ek sürümü ( örneğin, "5.2.7-extra" için '-extra'dır. ). Çoğunlukla
  paket dağıtımlarında paket sürümünü belirtmek için kullanılır.


id: PHP_FD_SETSIZE
type: constant
doc:
<comment>Description:</comment>
  Sistem çağrıları dosyatanıtıcılarının azami sayısı. PHP 7.1.0'dan beri mevcuttur.


id: PHP_FLOAT_DIG
type: constant
doc:
<comment>Description:</comment>
  Yuvarlama kaybı olmaksızın gerçek ve tam sayıya ileri-geri dönüştürülebilen ondalık hane sayısı.
  PHP 7.2.0'dan beri mevcuttur.


id: PHP_FLOAT_EPSILON
type: constant
doc:
<comment>Description:</comment>
  Gösterilebilen en küçük pozitif sayı. Bu x ise: <return>x + 1.0 != 1.0</return>. PHP 7.2.0'dan beri mevcuttur.


id: PHP_FLOAT_MAX
type: constant
doc:
<comment>Description:</comment>
  Gösterilebilen en büyük pozitif gerçek sayı. PHP 7.2.0'dan beri mevcuttur.


id: PHP_FLOAT_MIN
type: constant
doc:
<comment>Description:</comment>
  Gösterilebilen en küçük pozitif gerçek sayı. Gösterilebilen en küçük negatif gerçek sayıya
  ihtiyacınız varsa <return>- PHP_FLOAT_MAX</return> kullanın. PHP 7.2.0'dan beri mevcuttur.


id: PHP_INT_MAX
type: constant
doc:
<comment>Description:</comment>
  PHP derlenirken desteklenen en büyük tamsayı. Normalde int(2147483647).


id: PHP_INT_MIN
type: constant
doc:
<comment>Description:</comment>
  PHP derlenirken desteklenen en küçük tamsayı. Normalde 32 bitlik sistemlerde int(-2147483647), 64
  bitlik sistemlerde int(-9223372036854775808)'dir (PHP_INT_MIN === ~PHP_INT_MAX). PHP 7.0.0'dan
  beri mevcuttur.


id: PHP_MAJOR_VERSION
type: constant
doc:
<comment>Description:</comment>
  Şu anki ana sürüm bir numara ile gösterilmektedir (örneğin, "5.2.7-extra" için ana sürüm
  int(5)'tir).


id: PHP_MAXPATHLEN
type: constant
doc:
<comment>Description:</comment>
  PHP derlenirken desteklenen en uzun dosya isminin (dosya yolu dahil) boyu.


id: PHP_MINOR_VERSION
type: constant
doc:
<comment>Description:</comment>
  Şu anki alt sürüm bir numara ile gösterilmektedir (örneğin, "5.2.7-extra" için alt sürüm
  int(2)'dir).


id: PHP_OS_FAMILY
type: constant
doc:
<comment>Description:</comment>
  PHP ailesinin kullanıldığı işletim sistemi. <return>'Windows'</return>, <return>'BSD'</return>, <return>'Darwin'</return>, <return>'Solaris'</return>, <return>'Linux'</return> veya
  <return>'Unknown'</return> olabilir. PHP 7.2.0 ve sonrasinda kullanılabilir.


id: PHP_OUTPUT_HANDLER_CLEANABLE
type: constant
doc:
<comment>Description:</comment>
  <strong>ob_start()</strong> tarafından oluşturulan bir çıktı tamponunun temizlenebilirliğini denetler.


id: PHP_OUTPUT_HANDLER_CONT
type: constant
doc:
<comment>Description:</comment>
  Çıktı tamponunu boşaltıldığını ancak çıktı tamponlamanın süreceğini gösterir.
  
  Bu sabit <info>PHP_OUTPUT_HANDLER_WRITE</info> sabitinin takma adıdır.


id: PHP_OUTPUT_HANDLER_END
type: constant
doc:
<comment>Description:</comment>
  Çıktı tamponlamanın bittiğini gösterir.
  
  Bu sabit <info>PHP_OUTPUT_HANDLER_FINAL</info> sabitinin takma adıdır.


id: PHP_OUTPUT_HANDLER_FLUSHABLE
type: constant
doc:
<comment>Description:</comment>
  <strong>ob_start()</strong> tarafından oluşturulan bir çıktı tamponunun boşaltılabilirliğini denetler.


id: PHP_OUTPUT_HANDLER_REMOVABLE
type: constant
doc:
<comment>Description:</comment>
  <strong>ob_start()</strong> tarafından oluşturulan bir çıktı tamponunun betik sonlanmadan önce silinebilirliğini
  denetler.


id: PHP_OUTPUT_HANDLER_STDFLAGS
type: constant
doc:
<comment>Description:</comment>
  Öntanımlı çıktı tamponu seçeneklerinin tamamı; şuna eşdeğerdir: <info>PHP_OUTPUT_HANDLER_CLEANABLE</info> |
  <info>PHP_OUTPUT_HANDLER_FLUSHABLE</info> | <info>PHP_OUTPUT_HANDLER_REMOVABLE</info>.


id: PHP_OUTPUT_HANDLER_WRITE
type: constant
doc:
<comment>Description:</comment>
  Çıktı tamponunun boşaltılacağını ve çıktılanacak verilerin bulunduğunu gösterir.


id: PHP_PREFIX
type: constant
doc:
<comment>Description:</comment>
  Yapılandırma sırasında atanan --prefix değeri. Windows'ta bu değer yapılandırma sırasında
  --with-prefix ile atanır.


id: PHP_QUERY_RFC1738
type: constant
doc:
<comment>Description:</comment>
  Kodlama, boşlukların artı (<return>+</return>) işaretleri olarak kodlandığı  RFC 1738 ve
  <return>application/x-www-form-urlencoded</return> ortam türüne göre uygulanır.


id: PHP_QUERY_RFC3986
type: constant
doc:
<comment>Description:</comment>
  Kodlama, boşlukların yüzdeli (<return>%20</return>) kodlandığı RFC 3986'ya göre uygulanır.


id: PHP_RELEASE_VERSION
type: constant
doc:
<comment>Description:</comment>
  Şu anki dağıtım sürümü bir numara ile gösterilmektedir (örneğin, "5.2.7-extra" için dağıtım sürüm
  int(7)'dir).


id: PHP_SAPI
type: constant
doc:
<comment>Description:</comment>
  PHP derlenirken kullanılan sunucu API'si. Ayrıca bakınız: <strong>php_sapi_name()</strong>.


id: PHP_SESSION_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Oturumlar etkin ve bir oturum varsa <strong>session_status()</strong> işlevinin dönüş değeri.


id: PHP_SESSION_DISABLED
type: constant
doc:
<comment>Description:</comment>
  Oturumlar iptal edildiği takdirde <strong>session_status()</strong> işlevinin dönüş değeri.


id: PHP_SESSION_NONE
type: constant
doc:
<comment>Description:</comment>
  Oturumlar etkin olduğu halde hiç oturum yoksa <strong>session_status()</strong> işlevinin dönüş değeri.


id: PHP_SHLIB_SUFFIX
type: constant
doc:
<comment>Description:</comment>
  Derleme platformunun paylaşımlı kütüphane soneki. Normalde Unix'ler için "so", Windows için
  "dll"dir.


id: PHP_URL_FRAGMENT
type: constant
doc:
<comment>Description:</comment>
  Ayrıştırılan URL'nin fragmanını (# iminden sonraki dizge) çıktılar.


id: PHP_VERSION
type: constant
doc:
<comment>Description:</comment>
  Şu anki PHP sürüm numarası "ana.alt.dağıtım[ek]" gösterimine sahiptir.


id: PHP_VERSION_ID
type: constant
doc:
<comment>Description:</comment>
  Bir tamsayı olarak geçerli PHP sürümü ( örneğin, "5.2.7-extra" için int(50207)'dir. ). Sürüm
  karşılaştırması için faydalıdır.


id: PHP_WINDOWS_EVENT_CTRL_BREAK
type: constant
doc:
<comment>Description:</comment>
  Windows <return>CTRL+BREAK</return> olayı. PHP 7.4.0'dan itibaren kullanılabilir (sadece Windows).


id: PHP_WINDOWS_EVENT_CTRL_C
type: constant
doc:
<comment>Description:</comment>
  Windows <return>CTRL+C</return> olayı. PHP 7.4.0'dan itibaren kullanılabilir (sadece Windows).


id: PHP_WINDOWS_NT_SERVER
type: constant
doc:
<comment>Description:</comment>
  Bir sunucu sistemi belirtir (Server 2008/2003/2000 gibi); ancak, sunucu aynı zamanda bir etki
  alanı denetleyicisi ise <info>PHP_WINDOWS_NT_DOMAIN_CONTROLLER</info> olarak raporlanır.


id: PHP_WINDOWS_VERSION_BUILD
type: constant
doc:
<comment>Description:</comment>
  Windows derleme sürümü (örneğin, Windows Vista + SP1 için 6001'dir).


id: PHP_WINDOWS_VERSION_MAJOR
type: constant
doc:
<comment>Description:</comment>
  Windows ana sürüm numarası; <return>4</return> (NT4/Me/98/95), <return>5</return> (XP/2003 R2/2003/2000) veya <return>6</return> (Vista/2008/7/8/8.1)
  olabilir.


id: PHP_WINDOWS_VERSION_MINOR
type: constant
doc:
<comment>Description:</comment>
  Windows alt sürüm numarası; <return>0</return> (Vista/2008/2000/NT4/95), <return>1</return> (XP), <return>2</return> (2003 R2/2003/XP x64), <return>10</return> (98)
  veya <return>90</return> (ME) olabilir.


id: PHP_WINDOWS_VERSION_PLATFORM
type: constant
doc:
<comment>Description:</comment>
  PHP'nin üzerinde çalıştığı platform sürüm numarası;  Windows Vista/XP/2000/NT4 ve Server 2008/2003
  için <return>2</return>, Windows ME/98/95 için <return>1</return> olabilir.


id: PHP_WINDOWS_VERSION_PRODUCTTYPE
type: constant
doc:
<comment>Description:</comment>
  This contains the value used to determine the <return>PHP_WINDOWS_NT_*</return> sabitlerini saptamakta kullanılan
  değer; platform türünü belirleyen <return>PHP_WINDOWS_NT_*</return>sabitlerinden biri olabilir.


id: PHP_WINDOWS_VERSION_SP_MAJOR
type: constant
doc:
<comment>Description:</comment>
  Kurulu SP ana sürümü; hiçbir SP kurulu değilse <return>0</return>'dır. Örneğin SP 3 kurulu Windows XP için bu değer
  <return>3</return>'tür.


id: PHP_WINDOWS_VERSION_SP_MINOR
type: constant
doc:
<comment>Description:</comment>
  Kurulu SP ana sürümü; hiçbir SP kurulu değilse <return>0</return>'dır.


id: PHP_WINDOWS_VERSION_SUITEMASK
type: constant
doc:
<comment>Description:</comment>
  Çeşitli kurulu Windows özelliklerini betimleyen bir bit maskesi, Olası değerler için aşağıdaki
  tabloya  bakınız.


id: PKCS7_BINARY
type: constant
doc:
<comment>Description:</comment>
  Normalde girdi iletisi, (S/MIME belirtiminin gereği olarak) satırsonu karakteri olarak <return>CR</return> ve <return>LF</return>
  kullanan "meşru" biçeme dönüştürülür. Bu seçenek kullanıldığı takdirde hiçbir dönüşüm yapılmaz.
  MIME biçeminde olmayan ikil verilerle çalışırken yararlıdır.


id: PKCS7_DETACHED
type: constant
doc:
<comment>Description:</comment>
  Bir ileti imzalanırken MIME türü <return>"multipart/signed"</return> olan salt metin imzalama yapılır.
  <strong>openssl_pkcs7_sign()</strong> işlevinin <strong>$seçenekler</strong> bağımsız değişkeninde hiçbir şey belirtmezseniz
  öntanımlı olarak bu uygulanır. Bu seçeneği belirtmezseniz ileti şeffaf olmayan bir biçimde
  imzalanır, ancak eposta aktarımlarına karşı daha dayanıklı olmakla birlikte, ileti S/MIME desteği
  olmayan eposta araçları ile okunamaz.


id: PKCS7_NOATTR
type: constant
doc:
<comment>Description:</comment>
  Normalde bir ileti imzalanırken desteklenen bakışımlı algoritmalar ve imzalama zamanı dahil bazı
  öznitelikler iletiye eklenir. Bu seçenek belirtilmişse bunlar iletiye eklenmez.


id: PKCS7_NOCERTS
type: constant
doc:
<comment>Description:</comment>
  Bir ileti imzalanırken normal olarak imzalama sertifikası iletiye eklenir. Bu seçenek
  belirtilmişse eklenmez. Böylece imzalanan iletinin boyu küçülmüş olur, ancak doğrulayıcının
  imzalama sertifikasının bir kopyasına sahip olması gerekir (örneğin, <strong>openssl_pkcs7_verify()</strong>
  işlevinin <strong>$ek_sertifikalar</strong> bağımsız değişkeninde aktarılabilir).


id: PKCS7_NOCHAIN
type: constant
doc:
<comment>Description:</comment>
  İmzalama setifikalarına zincir doğrulama yapılmaz; yani, imzalı iletideki sertifikalar güvencesiz
  CA olarak kullanılmaz.


id: PKCS7_NOINTERN
type: constant
doc:
<comment>Description:</comment>
  Bir ileti doğrulanırken iletiye dahil edilmiş  sertifikalar varsa bunlar imzalama sertifikaları
  olarak ele alınır. Bu seçenekle sadece <strong>openssl_pkcs7_verify()</strong> işlevinin <strong>$ek_sertifikalar</strong> bağımsız
  değişkeninde belirtilen sertifikalar kullanılır. Bununla birlikte, sağlanan sertifikalar hala
  güvencesiz CA olarak kullanılabilir.


id: PKCS7_TEXT
type: constant
doc:
<comment>Description:</comment>
  Şifreli/imzalı iletiye başlıklar <return>text/plain</return> içerik türüyle eklenir. Şifre çözme veya doğrulama
  yapılacaksa bu başlıklar çıktıdan ayıklanır; eğer şifresi çözülecek veya doğrulanacak iletinin
  MIME türü <return>text/plain</return> değilse bir hata oluşur.


id: PNG_ALL_FILTERS
type: constant
doc:
<comment>Description:</comment>
  <strong>imagepng()</strong> işlevince kullanılan özel bir PNG süzgeci.


id: POSIX_RLIMIT_AS
type: constant
doc:
<comment>Description:</comment>
  Sürecin adres alanının bayt cinsinden azami boyutu. Ayrıca, PHP'nin memory_limit yapılandırma
  yönergesine de bakın.


id: POSIX_RLIMIT_CORE
type: constant
doc:
<comment>Description:</comment>
  İşletim sistemi hata döküm (core) dosyasının azami boyutu. 0 atanırsa bu dosya üretilmez.


id: POSIX_RLIMIT_CPU
type: constant
doc:
<comment>Description:</comment>
  Sürecin kullanabileceği işlemci zamanının saniye cinsinden azami miktarı. Yazılımsal sınıra
  ulaşılırsa <strong>pcntl_signal()</strong> işlevi ile yakalanabilen <return>SIGXCPU</return> sinyali gönderilir. İşletim sistemine
  bağlı olarak, donanımsal sınıra ulaşılana kadar her saniyede bir ek bir <return>SIGXCPU</return> sinyali gönerilir,
  bu noktaya ulaşıldığında yakalanamayebilen <return>SIGKILL</return> sinyali gönderilir.
  
  Ayrıca, <strong>set_time_limit()</strong> işlevine de bakınız.


id: POSIX_RLIMIT_DATA
type: constant
doc:
<comment>Description:</comment>
  Sürecin veri segmanının bayt cinsinden azami boyutu. <strong>brk()</strong> veya <strong>sbrk()</strong> işlevlerini kullanmakta
  olan bir eklenti olmadıkça bunun PHP'nin çalışmasına etkisi oldukça düşüktür.


id: POSIX_RLIMIT_KQUEUES
type: constant
doc:
<comment>Description:</comment>
  Bu kullanıcı kimliğinin oluşturmasına izin verilen azami kuyruk sayısı (FreeBSD). PHP 8.1.0 ve
  sonrasında kullanılabilir.


id: POSIX_RLIMIT_LOCKS
type: constant
doc:
<comment>Description:</comment>
  Sürecin oluşturabileceği azami kilit sayısı. Bu sadece oldukça eski sürümlü Linux çekirdeklerinde
  desteklenir.


id: POSIX_RLIMIT_MSGQUEUE
type: constant
doc:
<comment>Description:</comment>
  POSIX mesaj kuyrukları için ayrılabilen azami bayt sayısı. PHP, POSIX mesaj kuyrukları desteğiyle
  gelmediği için bu desteği özellikle kullanan bir eklenti olmadıkça bu sınırın bir etkisi
  olmayacaktır.


id: POSIX_RLIMIT_NICE
type: constant
doc:
<comment>Description:</comment>
  Sürecin yeniden tanımlanabilen nice önceliğinin azami miktarı. Bu değer <return>20 - sınır</return> şeklinde
  kullanılacağından negatif olmamalıdır.


id: POSIX_RLIMIT_NOFILE
type: constant
doc:
<comment>Description:</comment>
  Süreç tarafından açılabilen dosya tanıtıcıların azami sayısının bir fazlası.


id: POSIX_RLIMIT_NPROC
type: constant
doc:
<comment>Description:</comment>
  Sürecin gerçek kullanıcı kimliğini kullanmak üzere oluşturulabilen azami süreç (bazı sistemlerde
  evrelerin de) sayısı.


id: POSIX_RLIMIT_NPTS
type: constant
doc:
<comment>Description:</comment>
  Bu kullanıcı kimliğinin oluşturmasına izin verilen azami sözde uçbirim sayısı (FreeBSD).  PHP
  8.1.0 ve sonrasında kullanılabilir.


id: POSIX_RLIMIT_RTPRIO
type: constant
doc:
<comment>Description:</comment>
  <strong>sched_setscheduler()</strong> ve <strong>sched_setparam()</strong> çağrılarıyla atanabilen azami gerçek zamanlılık önceliği.


id: POSIX_RLIMIT_RTTIME
type: constant
doc:
<comment>Description:</comment>
  Gerçek zamanlılık zamanlamasının kullanılması durumunda engelleyici bir sistem çağrısı
  yapılmaksızın sürecin tüketebileceği işlemci zamanının mikro saniye cinsinden azami miktarı.


id: POSIX_RLIMIT_SIGPENDING
type: constant
doc:
<comment>Description:</comment>
  Sürecin gerçek kullanıcı kimliğiyle kuyruklayabileceği azami sinyal sayısı.


id: PREG_BACKTRACK_LIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek,  geriye doğru izleme sınırına ulaşılmışsa <strong>preg_last_error()</strong> işlevi tarafından
  döndürülür.


id: PREG_BAD_UTF8_ERROR
type: constant
doc:
<comment>Description:</comment>
  Son hata bozuk bir UTF-8 verisinden kaynaklanmışsa bu seçenek <strong>preg_last_error()</strong> işlevi tarafından
  döndürülür. (Bu sadece düzenli ifade UTF-8 kipinde çalışıyorsa mümkündür.)


id: PREG_BAD_UTF8_OFFSET_ERROR
type: constant
doc:
<comment>Description:</comment>
  Başlangıç, geçerli bir UTF-8 kodun başlangıcı değilse bu seçenek <strong>preg_last_error()</strong> işlevi
  tarafından döndürülür. (Bu sadece düzenli ifade  UTF-8 kipinde çalışıyorsa mümkündür.)


id: PREG_INTERNAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Dahili bir PCRE hatası oluşmuşsa <strong>preg_last_error()</strong> işlevi tarafından döndürülür.


id: PREG_JIT_STACKLIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Sınırlı JIT yığıt alanından dolayı son PCRE işlevi başarısız olmuşsa <strong>preg_last_error()</strong> işlevinden
  bu sabit döner.


id: PREG_NO_ERROR
type: constant
doc:
<comment>Description:</comment>
  Hiçbir hata oluşmamışsa <strong>preg_last_error()</strong> işlevi tarafından döndürülür.


id: PREG_OFFSET_CAPTURE
type: constant
doc:
<comment>Description:</comment>
  <info>PREG_SPLIT_OFFSET_CAPTURE</info> sabitinin açıklamasına bakın.


id: PREG_PATTERN_ORDER
type: constant
doc:
<comment>Description:</comment>
  Sonuçlar sıralanır. Yani, $eşleşen[0] şablonla eşleşen dizgenin tamamını, $eşleşen[1] ilk
  parantezli grupla eşleşen alt dizgeyi, $eşleşen[2] ikincisini, vb. içerir. Bu seçenek sadece
  <strong>preg_match_all()</strong> işlevi ile kullanılır.


id: PREG_RECURSION_LIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek, iç içelik sınırına ulaşılmışsa <strong>preg_last_error()</strong> işlevi tarafından döndürülür.


id: PREG_SET_ORDER
type: constant
doc:
<comment>Description:</comment>
  Sonuçlar sıralanır. Yani, $eşleşen[0] şablonla eşleşen ilk kümeyi, $eşleşen[2] ikincisini, vb.
  içerir. Bu seçenek sadece <strong>preg_match_all()</strong> işlevi ile kullanılır.


id: PREG_SPLIT_DELIM_CAPTURE
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek <strong>preg_split()</strong> işlevinin ayraçlı şablon içindeki parantezli grupları da yakalamasını
  sağlar


id: PREG_SPLIT_NO_EMPTY
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek <strong>preg_split()</strong> işlevinin sadece boş olmayan parçaları döndürmesini sağlar.


id: PREG_SPLIT_OFFSET_CAPTURE
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek etkinse, her eşleşmede ayrıca sona eklenen dizgenin başlangıcı da döndürülür. Bu, dizi
  içindeki dönüş değerini değiştirir. Böylece dizinin her elemanı 0. başlangıçtan itibaren eşleşen
  dizgeyi ve 1. başlangıca konu dizge başlangıcını içeren bir dizi içerir. Bu seçenek sadece
  <strong>preg_split()</strong> için kullanılabilmektedir.


id: PREG_UNMATCHED_AS_NULL
type: constant
doc:
<comment>Description:</comment>
  Bu seçenek <strong>preg_match()</strong> ve <strong>preg_match_all()</strong> işlevlerinin eşleşmeyen alt şablonların $eşleşmeler
  içinde  <info>null</info> değerlerle içerileceğini belirtir. Bu bayrak olmaksızın eşleşmeyen alt şablonlar boş
  eşleşmelermiş gibi boş dizgeler olarak raporlanır. Bu bayrak bu iki durumun ayırd edilebilmesini
  sağlar. Bu seçenek PHP 7.2.0'dan beri kullanılabilmektedir.


id: PSFS_ERR_FATAL
type: constant
doc:
<comment>Description:</comment>
  Kullanıcı tanımlı süzgecin kurtarılamayacak bir hata tespit ettiğini ve devam edilemeyeceğini
  belirten dönüş kodu.


id: PSFS_FEED_ME
type: constant
doc:
<comment>Description:</comment>
  Kullanıcı tanımlı süzgecin veriyi başarıyla işlediğini fakat döndürülecek veri olmadığını belirten
  dönüş kodu.


id: PSFS_PASS_ON
type: constant
doc:
<comment>Description:</comment>
  Kullanıcı tanımlı süzgecin veriyi başarıyla işleyip biriktirici zincirini <strong>$out</strong>  bağımsız
  değişkenine yerleştirdiğini belirten donüş kodu.


id: PSpell\Config
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces a <return>pspell config</return> resource as of PHP 8.1.0.


id: PSpell\Dictionary
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces a <return>pspell</return> resource as of PHP 8.1.0.


id: PTHREADS_ALLOW_HEADERS
type: constant
doc:
<comment>Description:</comment>
  Allow new Threads to send headers to standard output (normally prohibited)


id: PTHREADS_INHERIT_ALL
type: constant
doc:
<comment>Description:</comment>
  The default options for all Threads, causes pthreads to copy the environment when new Threads are
  started


id: ParentIterator
type: class
doc:
<comment>Description:</comment>
  This extended <class>FilterIterator</class> allows a recursive iteration using <class>RecursiveIteratorIterator</class> that
  only shows those elements which have children.


id: ParentIterator::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a ParentIterator
  
  Constructs a <class>ParentIterator</class> on an iterator.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>RecursiveIterator</info>  <strong>$iterator</strong>  The iterator being constructed upon.


id: ParentIterator::accept
type: function
doc:
<comment>Description:</comment>
  Determines acceptability
  
  Determines if the current element has children.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the current element is acceptable, otherwise <info>false</info>.

<comment>See Also:</comment>
   * ParentIterator::hasChildren
   * FilterIterator::accept


id: ParentIterator::getChildren
type: function
doc:
<comment>Description:</comment>
  Return the inner iterator's children contained in a ParentIterator
  
  Get the inner iterator's children contained in a ParentIterator.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>ParentIterator</info>  An <info>object</info>.


id: ParentIterator::hasChildren
type: function
doc:
<comment>Description:</comment>
  Check whether the inner iterator's current element has children
  
  Check whether the inner iterator's current element has children.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: ParentIterator::next
type: function
doc:
<comment>Description:</comment>
  Move the iterator forward
  
  Moves the iterator forward.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: ParentIterator::rewind
type: function
doc:
<comment>Description:</comment>
  Rewind the iterator
  
  Rewinds the iterator.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\ErrorInfo
type: class
doc:
<comment>Description:</comment>
  The class represents detailed error information as supplied by Parle\Parser::errorInfo


id: Parle\INTERNAL_UTF32
type: constant
doc:
<comment>Description:</comment>
  Flag whether the internal UTF-32 support is compiled in. Available since parle 0.7.2.


id: Parle\Lexer
type: class
doc:
<comment>Description:</comment>
  Single state lexer class. Lexemes can be defined on the fly. If the particular lexer instance is
  meant to be used with <class>Parle\Parser</class>, the token IDs need to be taken from there. Otherwise,
  arbitrary token IDs can be supplied. This lexer can give a certain performance advantage over
  <class>Parle\RLexer</class>, if no multiple states are required. Note, that <class>Parle\RParser</class> is not compatible with
  this lexer.


id: Parle\Lexer::advance
type: function
doc:
<comment>Description:</comment>
  Process next lexer rule
  
  Processes the next rule and prepares the resulting token data.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::build
type: function
doc:
<comment>Description:</comment>
  Finalize the lexer rule set
  
  Rules, previously added with Parle\Lexer::push are finalized. This method call has to be done
  after all the necessary rules was pushed. The rule set becomes read only. The lexing can begin.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::callout
type: function
doc:
<comment>Description:</comment>
  Define token callback
  
  Define a callback to be invoked once lexer encounters a particular token.

<comment>Param:</comment>
  <info>int</info>       <strong>$id</strong>        Token id.
  <info>callable</info>  <strong>$callback</strong>  Callable to be invoked. The callable doesn't receive any arguments and its
                       return value is ignored.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::consume
type: function
doc:
<comment>Description:</comment>
  Pass the data for processing
  
  Consume the data for lexing.

<comment>Param:</comment>
  <info>string</info>  <strong>$data</strong>  Data to be lexed.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::dump
type: function
doc:
<comment>Description:</comment>
  Dump the state machine
  
  Dump the current state machine to stdout.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::getToken
type: function
doc:
<comment>Description:</comment>
  Retrieve the current token
  
  Retrieve the current token.

<comment>Return:</comment>
  <info>Parle\Token</info>  Returns an instance of <class>Parle\Token</class>.


id: Parle\Lexer::insertMacro
type: function
doc:
<comment>Description:</comment>
  Insert regex macro
  
  Insert a regex macro, that can be later used as a shortcut and included in other regular
  expressions.

<comment>Param:</comment>
  <info>string</info>  <strong>$name</strong>   Name of the macros.
  <info>string</info>  <strong>$regex</strong>  Regular expression.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::push
type: function
doc:
<comment>Description:</comment>
  Add a lexer rule
  
  Push a pattern for lexeme recognition.

<comment>Param:</comment>
  <info>string</info>  <strong>$regex</strong>  Regular expression used for token matching.
  <info>int</info>     <strong>$id</strong>     Token id. If the lexer instance is meant to be used standalone, this can be an
                  arbitrary number. If the lexer instance is going to be passed to the parser, it
                  has to be an id returned by Parle\Parser::tokenid.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Lexer::reset
type: function
doc:
<comment>Description:</comment>
  Reset lexer
  
  Reset lexing optionally supplying the desired offset.

<comment>Param:</comment>
  <info>int</info>  <strong>$pos</strong>  Reset position.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser
type: class
doc:
<comment>Description:</comment>
  Parser class. Rules can be defined on the fly. Once finalized, a <class>Parle\Lexer</class> instance is required
  to deliver the token stream.


id: Parle\Parser::advance
type: function
doc:
<comment>Description:</comment>
  Process next parser rule
  
  Process next parser rule.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::build
type: function
doc:
<comment>Description:</comment>
  Finalize the grammar rules
  
  Any tokens and grammar rules previously added are finalized. The rule set becomes readonly and the
  parser is ready to start.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::consume
type: function
doc:
<comment>Description:</comment>
  Consume the data for processing
  
  Consume the data for parsing.

<comment>Param:</comment>
  <info>string</info>       <strong>$data</strong>   Data to be parsed.
  <info>Parle\Lexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                       grammar.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::dump
type: function
doc:
<comment>Description:</comment>
  Dump the grammar
  
  Dump the current grammar to stdout.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::errorInfo
type: function
doc:
<comment>Description:</comment>
  Retrieve the error information
  
  Retrieve the error information in case Parle\Parser::action returned the error action.

<comment>Return:</comment>
  <info>Parle\ErrorInfo</info>  Returns an instance of <class>Parle\ErrorInfo</class>.


id: Parle\Parser::left
type: function
doc:
<comment>Description:</comment>
  Declare a token with left-associativity
  
  Declare a terminal with left associativity.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::nonassoc
type: function
doc:
<comment>Description:</comment>
  Declare a token with no associativity
  
  Declare a terminal, that cannot appear more than once in the row.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::precedence
type: function
doc:
<comment>Description:</comment>
  Declare a precedence rule
  
  Declares a precedence rule for a fictitious terminal symbol. This rule can be later used in the
  specific grammar rules.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::push
type: function
doc:
<comment>Description:</comment>
  Add a grammar rule
  
  Push a grammar rule. The production id returned can be used later in the parsing process to
  identify the rule matched.

<comment>Param:</comment>
  <info>string</info>  <strong>$name</strong>  Rule name.
  <info>string</info>  <strong>$rule</strong>  The rule to be added. The syntax is Bison compatible.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the rule index.


id: Parle\Parser::reset
type: function
doc:
<comment>Description:</comment>
  Reset parser state
  
  Reset parser state using the given token id.

<comment>Param:</comment>
  <info>int</info>  <strong>$tokenId</strong>  Token id.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::right
type: function
doc:
<comment>Description:</comment>
  Declare a token with right-associativity
  
  Declare a terminal with right associativity.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::sigil
type: function
doc:
<comment>Description:</comment>
  Retrieve a matching part of a rule
  
  Retrieve a part of the match by a rule. This method is equivalent to the pseudo variable
  functionality in Bison.

<comment>Param:</comment>
  <info>int</info>  <strong>$idx</strong>  Match index, zero based.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the matched part.


id: Parle\Parser::sigilCount
type: function
doc:
<comment>Description:</comment>
  Number of elements in matched rule
  
  Get number of elements in the matched rule.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info>


id: Parle\Parser::sigilName
type: function
doc:
<comment>Description:</comment>
  Retrieve a rule or token name
  
  Retrieve a partial rule name or token name corresponding to the sigil index.

<comment>Param:</comment>
  <info>int</info>  <strong>$idx</strong>  Match index, zero based.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the matched part.


id: Parle\Parser::token
type: function
doc:
<comment>Description:</comment>
  Declare a token
  
  Declare a terminal to be used in the grammar.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Parser::tokenId
type: function
doc:
<comment>Description:</comment>
  Get token id
  
  Retrieve the id of the named token.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Name of the token as used in Parle\Parser::token.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the token id.


id: Parle\Parser::trace
type: function
doc:
<comment>Description:</comment>
  Trace the parser operation
  
  Retrieve the current parser operation description. This can be especially useful for studying the
  parser and to optimize the grammar.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the trace information.


id: Parle\Parser::validate
type: function
doc:
<comment>Description:</comment>
  Validate input
  
  Validate an input string. The string is parsed internally, thus this method is useful for the
  quick input validation.

<comment>Param:</comment>
  <info>string</info>       <strong>$data</strong>   String to be validated.
  <info>Parle\Lexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                       grammar.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>bool</info> witnessing whether the input chimes or not with the defined rules.


id: Parle\RLexer
type: class
doc:
<comment>Description:</comment>
  Multistate lexer class. Lexemes can be defined on the fly. If the particular lexer instance is
  meant to be used with <class>Parle\RParser</class>, the token IDs need to be taken from there. Otherwise,
  arbitrary token IDs can be supplied. Note, that <class>Parle\Parser</class> is not compatible with this lexer.


id: Parle\RLexer::build
type: function
doc:
<comment>Description:</comment>
  Finalize the lexer rule set
  
  Rules, previously added with Parle\RLexer::push are finalized. This method call has to be done
  after all the necessary rules was pushed. The rule set becomes read only. The lexing can begin.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\RLexer::getToken
type: function
doc:
<comment>Description:</comment>
  Retrieve the current token
  
  Retrive the current token.

<comment>Return:</comment>
  <info>Parle\Token</info>  Returns an instance of <class>Parle\Token</class>.


id: Parle\RLexer::push
type: function
doc:
<comment>Description:</comment>
  Add a lexer rule
  
  Push a pattern for lexeme recognition.
  
  A 'start state' and 'exit state' can be specified by using a suitable signature.

<comment>Param:</comment>
  <info>string</info>  <strong>$regex</strong>     Regular expression used for token matching.
  <info>int</info>     <strong>$id</strong>        Token id. If the lexer instance is meant to be used standalone, this can be an
                     arbitrary number. If the lexer instance is going to be passed to the parser, it
                     has to be an id returned by Parle\RParser::tokenid.
  <info>string</info>  <strong>$state</strong>     State name. If '*' is used as start state, then the rule is applied to all
                     lexer states.
  <info>string</info>  <strong>$newState</strong>  New state name, after the rule was applied.
                     
                     If '.' is specified as the exit state, then the lexer state is unchanged when
                     that rule matches. An exit state with '&gt;' before the name means push. Use
                     the signature without id for either continuation or to start matching, when a
                     continuation or recursion is required.
                     
                     If '\<' is specified as exit state, it means pop. In that case, the signature containing the id can be used to identify the match. Note that even in the case an id is specified, the rule will finish first when all the previous pushes popped.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\RLexer::pushState
type: function
doc:
<comment>Description:</comment>
  Push a new start state
  
  This lexer type can have more than one state machine. This allows you to lex different tokens
  depending on context, thus allowing simple parsing to take place. Once a state pushed, it can be
  used with a suitable Parle\RLexer::push signature variant.

<comment>Param:</comment>
  <info>string</info>  <strong>$state</strong>  Name of the state.

<comment>Return:</comment>
  <info>int</info>  


id: Parle\RParser
type: class
doc:
<comment>Description:</comment>
  Parser class. Rules can be defined on the fly. Once finalized, a <class>Parle\RLexer</class> instance is required
  to deliver the token stream.


id: Parle\RParser::advance
type: function
doc:
<comment>Description:</comment>
  Process next parser rule
  
  Prosess next parser rule.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\RParser::consume
type: function
doc:
<comment>Description:</comment>
  Consume the data for processing
  
  Consume the data for parsing.

<comment>Param:</comment>
  <info>string</info>  <strong>$data</strong>   Data to be parsed.
  <info></info>        <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular grammar.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\RParser::errorInfo
type: function
doc:
<comment>Description:</comment>
  Retrieve the error information
  
  Retrieve the error information in case Parle\RParser::action returned the error action.

<comment>Return:</comment>
  <info>Parle\ErrorInfo</info>  Returns an instance of <class>Parle\ErrorInfo</class>.


id: Parle\RParser::precedence
type: function
doc:
<comment>Description:</comment>
  Declare a precedence rule
  
  Declares a precedence rule for a fictious terminal symbol. This rule can be later used in the
  specific grammar rules.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\RParser::tokenId
type: function
doc:
<comment>Description:</comment>
  Get token id
  
  Retrieve the id of the named token.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Name of the token as used in Parle\RParser::token.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the token id.


id: Parle\RParser::trace
type: function
doc:
<comment>Description:</comment>
  Trace the parser operation
  
  Retrieve the current parser operation description. This can be especially useful to study the
  parser and to optimize the grammar.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the trace information.


id: Parle\RParser::validate
type: function
doc:
<comment>Description:</comment>
  Validate input
  
  Validate an input string. The string is parsed internally, thus this method is useful for the
  quick input validation.

<comment>Param:</comment>
  <info>string</info>        <strong>$data</strong>   String to be validated.
  <info>Parle\RLexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                        grammar.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>bool</info> whitnessing whether the input chimes or not with the defined rules.


id: Parle\Stack
type: class
doc:
<comment>Description:</comment>
  <class>Parle\Stack</class> is a LIFO stack. The elements are inserted and removed only from one end.


id: Parle\Stack::pop
type: function
doc:
<comment>Description:</comment>
  Pop an item from the stack

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Stack::push
type: function
doc:
<comment>Description:</comment>
  Push an item into the stack

<comment>Param:</comment>
  <info>mixed</info>  <strong>$item</strong>  Variable to be pushed.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Parle\Token
type: class
doc:
<comment>Description:</comment>
  This class represents a token. Lexer returns instances of this class.


id: PgSql\Connection
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces a <return>pgsql link</return> resource as of PHP 8.1.0.


id: PgSql\Lob
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces a <return>pgsql large object</return> resource as of PHP 8.1.0.


id: PgSql\Result
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces a <return>pgsql result</return> resource as of PHP 8.1.0.


id: Phar
type: class
doc:
<comment>Description:</comment>
  The Phar class provides a high-level interface to accessing and creating phar archives.


id: Phar::COMPRESSED
type: constant
doc:
<comment>Description:</comment>
  0x0000F000
  
  bitmask that can be used with file flags to determine if any compression is present


id: Phar::OPENSSL
type: constant
doc:
<comment>Description:</comment>
  signature with OpenSSL public/private key pair.  This is a true, asymmetric key signature.


id: Phar::PHP
type: constant
doc:
<comment>Description:</comment>
  used to instruct the mimeoverrides parameter of <strong>Phar::webPhar()</strong> that the extension should be
  parsed as a PHP file


id: Phar::PHPS
type: constant
doc:
<comment>Description:</comment>
  used to instruct the mimeoverrides parameter of <strong>Phar::webPhar()</strong> that the extension should be
  parsed as a PHP source file through <strong>highlight_file()</strong>


id: Phar::__construct
type: function
doc:
<comment>Description:</comment>
  Construct a Phar archive object

<comment>Param:</comment>
  <info>string</info>       <strong>$filename</strong>  Path to an existing Phar archive or to-be-created archive. The file name's
                          extension must contain .phar.
  <info>int</info>          <strong>$flags</strong>     Flags to pass to parent class <class>RecursiveDirectoryIterator</class>.
  <info>string|null</info>  <strong>$alias</strong>     Alias with which this Phar archive should be referred to in calls to
                          stream functionality.


id: Phar::addEmptyDir
type: function
doc:
<comment>Description:</comment>
  Add an empty directory to the phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  With this method, an empty directory is created with path <return>dirname</return>. This method is similar to
  <strong>ZipArchive::addEmptyDir()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$directory</strong>  The name of the empty directory to create in the phar archive

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>PharData::addEmptyDir()</strong>
   * <strong>Phar::addFile()</strong>
   * <strong>Phar::addFromString()</strong>


id: Phar::addFile
type: function
doc:
<comment>Description:</comment>
  Add a file from the filesystem to the phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  With this method, any file or URL can be added to the phar archive.  If the optional second
  parameter <strong>$localName</strong> is a <info>string</info>, the file will be stored in the archive with that name, otherwise
  the <return>file</return> parameter is used as the path to store within the archive.  URLs must have a localname or
  an exception is thrown. This method is similar to <strong>ZipArchive::addFile()</strong>.

<comment>Param:</comment>
  <info>string</info>       <strong>$filename</strong>   Full or relative path to a file on disk to be added to the phar archive.
  <info>string|null</info>  <strong>$localName</strong>  Path that the file will be stored in the archive.

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>Phar::offsetSet()</strong>
   * <strong>PharData::addFile()</strong>
   * <strong>Phar::addFromString()</strong>
   * <strong>Phar::addEmptyDir()</strong>


id: Phar::addFromString
type: function
doc:
<comment>Description:</comment>
  Add a file from a string to the phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  With this method, any string can be added to the phar archive. The file will be stored in the
  archive with <return>localname</return> as its path.  This method is similar to <strong>ZipArchive::addFromString()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  Path that the file will be stored in the archive.
  <info>string</info>  <strong>$contents</strong>   The file contents to store

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>Phar::offsetSet()</strong>
   * <strong>PharData::addFromString()</strong>
   * <strong>Phar::addFile()</strong>
   * <strong>Phar::addEmptyDir()</strong>


id: Phar::apiVersion
type: function
doc:
<comment>Description:</comment>
  Returns the api version
  
  Return the API version of the phar file format that will be used when creating phars.  The Phar
  extension supports reading API version 1.0.0 or newer.  API version 1.1.0 is required for SHA-256
  and SHA-512 hash, and API version 1.1.1 is required to store empty directories.

<comment>Return:</comment>
  <info>string</info>  The API version string as in <return>"1.0.0"</return>.


id: Phar::buildFromDirectory
type: function
doc:
<comment>Description:</comment>
  Construct a phar archive from the files within a directory
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Populate a phar archive from directory contents.  The optional second parameter is a regular
  expression (pcre) that is used to exclude files. Any filename that matches the regular expression
  will be included, all others will be excluded.  For more fine-grained control, use
  <strong>Phar::buildFromIterator()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$directory</strong>  The full or relative path to the directory that contains all files to add to
                      the archive.
  <info>string</info>  <strong>$pattern</strong>    An optional pcre regular expression that is used to filter the list of files.
                      Only file paths matching the regular expression will be included in the
                      archive.

<comment>Return:</comment>
  <info>array</info>  <strong>Phar::buildFromDirectory()</strong> returns an associative array mapping internal path of file to
         the full path of the file on the filesystem.

<comment>See Also:</comment>
   * <strong>Phar::buildFromIterator()</strong>


id: Phar::buildFromIterator
type: function
doc:
<comment>Description:</comment>
  Construct a phar archive from an iterator
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Populate a phar archive from an iterator.  Two styles of iterators are supported, iterators that
  map the filename within the phar to the name of a file on disk, and iterators like
  DirectoryIterator that return SplFileInfo objects.  For iterators that return SplFileInfo objects,
  the second parameter is required.

<comment>Param:</comment>
  <info>Traversable</info>  <strong>$iterator</strong>       Any iterator that either associatively maps phar file to location or
                               returns SplFileInfo objects
  <info>string|null</info>  <strong>$baseDirectory</strong>  For iterators that return SplFileInfo objects, the portion of each
                               file's full path to remove when adding to the phar archive

<comment>Return:</comment>
  <info>array</info>  <strong>Phar::buildFromIterator()</strong> returns an associative array mapping internal path of file to the
         full path of the file on the filesystem.

<comment>See Also:</comment>
   * <strong>Phar::buildFromDirectory()</strong>


id: Phar::canCompress
type: function
doc:
<comment>Description:</comment>
  Returns whether phar extension supports compression using either zlib or bzip2
  
  This should be used to test whether compression is possible prior to loading a phar archive
  containing compressed files.

<comment>Param:</comment>
  <info>int</info>  <strong>$compression</strong>  Either <return>Phar::GZ</return> or <return>Phar::BZ2</return> can be used to test whether compression is
                     possible with a specific compression algorithm (zlib or bzip2).

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if compression/decompression is available, <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>


id: Phar::canWrite
type: function
doc:
<comment>Description:</comment>
  Returns whether phar extension supports writing and creating phars
  
  This static method determines whether write access has been disabled in the system php.ini via the
  phar.readonly ini variable.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if write access is enabled, <info>false</info> if it is disabled.

<comment>See Also:</comment>
   * phar.readonly
   * <strong>Phar::isWritable()</strong>


id: Phar::compress
type: function
doc:
<comment>Description:</comment>
  Compresses the entire Phar archive using Gzip or Bzip2 compression
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  For tar-based and phar-based phar archives, this method compresses the entire archive using gzip
  compression or bzip2 compression.  The resulting file can be processed with the gunzip
  command/bunzip command, or accessed directly and transparently with the Phar extension.
  
  For Zip-based phar archives, this method fails with an exception. The zlib extension must be
  enabled to compress with gzip compression, the bzip2 extension must be enabled in order to
  compress with bzip2 compression. As with all functionality that modifies the contents of a phar,
  the phar.readonly INI variable must be off in order to succeed.
  
  In addition, this method automatically renames the archive, appending <return>.gz</return>, <return>.bz2</return> or removing the
  extension if passed <return>Phar::NONE</return> to remove compression.  Alternatively, a file extension may be
  specified with the second parameter.

<comment>Param:</comment>
  <info>int</info>          <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                             <return>Phar::NONE</return> to remove compression.
  <info>string|null</info>  <strong>$extension</strong>    By default, the extension is <return>.phar.gz</return> or <return>.phar.bz2</return> for compressing phar
                             archives, and <return>.phar.tar.gz</return> or <return>.phar.tar.bz2</return> for compressing tar
                             archives.  For decompressing, the default file extensions are <return>.phar</return> and
                             <return>.phar.tar</return>.

<comment>Return:</comment>
  <info>Phar|null</info>  Returns a <class>Phar</class> object, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::compressFiles
type: function
doc:
<comment>Description:</comment>
  Compresses all files in the current Phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  For tar-based phar archives, this method throws a <class>BadMethodCallException</class>, as compression of
  individual files within a tar archive is not supported by the file format.  Use <strong>Phar::compress()</strong>
  to compress an entire tar-based phar archive.
  
  For Zip-based and phar-based phar archives, this method compresses all files in the Phar archive
  using the specified compression. The zlib  or bzip2 extensions must be enabled to take advantage
  of this feature.  In addition, if any files are already compressed using bzip2/zlib compression,
  the respective extension must be enabled in order to decompress the files prior to re-compressing.
  As with all functionality that modifies the contents of a phar, the phar.readonly INI variable
  must be off in order to succeed.

<comment>Param:</comment>
  <info>int</info>  <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                     <return>Phar::NONE</return> to remove compression.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>


id: Phar::convertToData
type: function
doc:
<comment>Description:</comment>
  Convert a phar archive to a non-executable tar or zip file
  
  This method is used to convert an executable phar archive to either a tar or zip file.  To make
  the tar or zip non-executable, the phar stub and phar alias files are removed from the newly
  created archive.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class> if the archive is in phar
  file format.  For archives in tar or zip file format, this method converts the archive to a
  non-executable archive.
  
  If successful, the method creates a new archive on disk and returns a <class>PharData</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int|null</info>     <strong>$format</strong>       This should be one of <return>Phar::TAR</return> or <return>Phar::ZIP</return>.  If set to <info>null</info>, the
                             existing file format will be preserved.
  <info>int|null</info>     <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression,
                             <return>Phar::GZ</return> for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based
                             compression.
  <info>string|null</info>  <strong>$extension</strong>    This parameter is used to override the default file extension for a
                             converted archive.  Note that <return>.phar</return> cannot be used anywhere in the
                             filename for a non-executable tar or zip archive.
                             
                             If converting to a tar-based phar archive, the default extensions are
                             <return>.tar</return>, <return>.tar.gz</return>, and <return>.tar.bz2</return> depending on specified compression. For
                             zip-based archives, the default extension is <return>.zip</return>.

<comment>Return:</comment>
  <info>PharData|null</info>  The method returns a <class>PharData</class> object on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>PharData::convertToExecutable()</strong>
   * <strong>PharData::convertToData()</strong>


id: Phar::convertToExecutable
type: function
doc:
<comment>Description:</comment>
  Convert a phar archive to another executable phar archive file format
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This method is used to convert a phar archive to another file format.  For instance, it can be
  used to create a tar-based executable phar archive from a zip-based executable phar archive, or
  from an executable phar archive in the phar file format.  In addition, it can be used to apply
  whole-archive compression to a tar or phar-based archive.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class>.
  
  If successful, the method creates a new archive on disk and returns a <class>Phar</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int|null</info>     <strong>$format</strong>       This should be one of <return>Phar::PHAR</return>, <return>Phar::TAR</return>, or <return>Phar::ZIP</return>.  If set to
                             <info>null</info>, the existing file format will be preserved.
  <info>int|null</info>     <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression,
                             <return>Phar::GZ</return> for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based
                             compression.
  <info>string|null</info>  <strong>$extension</strong>    This parameter is used to override the default file extension for a
                             converted archive.  Note that all zip- and tar-based phar archives must
                             contain <return>.phar</return> in their file extension in order to be processed as a
                             phar archive.
                             
                             If converting to a phar-based archive, the default extensions are
                             <return>.phar</return>, <return>.phar.gz</return>, or <return>.phar.bz2</return> depending on the specified compression.
                             For tar-based phar archives, the default extensions are <return>.phar.tar</return>,
                             <return>.phar.tar.gz</return>, and <return>.phar.tar.bz2</return>.  For zip-based phar archives, the
                             default extension is <return>.phar.zip</return>.

<comment>Return:</comment>
  <info>Phar|null</info>  The method returns a <class>Phar</class> object on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToData()</strong>
   * <strong>PharData::convertToExecutable()</strong>
   * <strong>PharData::convertToData()</strong>


id: Phar::copy
type: function
doc:
<comment>Description:</comment>
  Copy a file internal to the phar archive to another new file within the phar
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Copy a file internal to the phar archive to another new file within the phar. This is an
  object-oriented alternative to using <strong>copy()</strong> with the phar stream wrapper.

<comment>Param:</comment>
  <info>string</info>  <strong>$from</strong>  
  <info>string</info>  <strong>$to</strong>    

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is safer to encase method call in a try/catch block and
        assume success if no exception is thrown.


id: Phar::count
type: function
doc:
<comment>Description:</comment>
  Returns the number of entries (files) in the Phar archive

<comment>Param:</comment>
  <info>int</info>  <strong>$mode</strong>  <strong>$mode</strong> is an integer value specifying the counting mode to be used. By default, it is
              set to <info>COUNT_NORMAL</info>, which counts only the number of items in the archive that have
              not been deleted or hidden. When set to <info>COUNT_RECURSIVE</info>, it counts all items in the
              archive, including those that have been deleted or hidden.

<comment>Return:</comment>
  <info>int</info>  The number of files contained within this phar, or <return>0</return> (the number zero) if none.


id: Phar::createDefaultStub
type: function
doc:
<comment>Description:</comment>
  Create a phar-file format specific stub
  
  This method is intended for creation of phar-file format-specific stubs, and is not intended for
  use with tar- or zip-based phar archives.
  
  Phar archives contain a bootstrap loader, or <return>stub</return> written in PHP that is executed when the archive
  is executed in PHP either via include:  ]]> or by simple execution:
  
  This method provides a simple and easy method to create a stub that will run a startup file from
  the phar archive.  In addition, different files can be specified for running the phar archive from
  the command line versus through a web server.  The loader stub also calls
  <strong>Phar::interceptFileFuncs()</strong> to allow easy bundling of a PHP application that accesses the file
  system.  If the phar extension is not present, the loader stub will extract the phar archive to a
  temporary directory and then operate on the files.  A shutdown function erases the temporary files
  on exit.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$index</strong>     Relative path within the phar archive to run if accessed on the
                          command-line
  <info>string|null</info>  <strong>$webIndex</strong>  Relative path within the phar archive to run if accessed through a web
                          browser

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the contents of a customized bootstrap loader (stub) that
          allows the created Phar archive to work with or without the Phar extension enabled.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>
   * <strong>Phar::getStub()</strong>


id: Phar::decompress
type: function
doc:
<comment>Description:</comment>
  Decompresses the entire Phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  For tar-based and phar-based phar archives, this method decompresses the entire archive.
  
  For Zip-based phar archives, this method fails with an exception. The zlib extension must be
  enabled to decompress an archive compressed with gzip compression, and the bzip2 extension must be
  enabled in order to decompress an archive compressed with bzip2 compression. As with all
  functionality that modifies the contents of a phar, the phar.readonly INI variable must be off in
  order to succeed.
  
  In addition, this method automatically changes the file extension of the archive, <return>.phar</return> by default
  for phar archives, or <return>.phar.tar</return> for tar-based phar archives. Alternatively, a file extension may
  be specified with the second parameter.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$extension</strong>  For decompressing, the default file extensions are <return>.phar</return> and <return>.phar.tar</return>.
                           Use this parameter to specify another file extension.  Be aware that all
                           executable phar archives must contain <return>.phar</return> in their filename.

<comment>Return:</comment>
  <info>Phar|null</info>  A <class>Phar</class> object is returned on success, and <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::decompressFiles
type: function
doc:
<comment>Description:</comment>
  Decompresses all files in the current Phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  For tar-based phar archives, this method throws a <class>BadMethodCallException</class>, as compression of
  individual files within a tar archive is not supported by the file format.  Use <strong>Phar::compress()</strong>
  to compress an entire tar-based phar archive.
  
  For Zip-based and phar-based phar archives, this method decompresses all files in the Phar
  archive. The zlib  or bzip2 extensions must be enabled to take advantage of this feature if any
  files are compressed using bzip2/zlib compression. As with all functionality that modifies the
  contents of a phar, the phar.readonly INI variable must be off in order to succeed.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>


id: Phar::delMetadata
type: function
doc:
<comment>Description:</comment>
  Deletes the global metadata of the phar
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Deletes the global metadata of the phar

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>Phar::getMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>


id: Phar::delete
type: function
doc:
<comment>Description:</comment>
  Delete a file within a phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Delete a file within an archive.  This is the functional equivalent of calling <strong>unlink()</strong> on the
  stream wrapper equivalent, as shown in the example below.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  Path within an archive to the file to delete.

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>PharData::delete()</strong>
   * <strong>Phar::unlinkArchive()</strong>


id: Phar::extractTo
type: function
doc:
<comment>Description:</comment>
  Extract the contents of a phar archive to a directory
  
  Extract all files within a phar archive to disk.  Extracted files and directories preserve
  permissions as stored in the archive.  The optional parameters allow optional control over which
  files are extracted, and whether existing files on disk can be overwritten. The second parameter
  <strong>$files</strong> can be either the name of a file or directory to extract, or an array of names of files and
  directories to extract.  By default, this method will not overwrite existing files, the third
  parameter can be set to true to enable overwriting of files. This method is similar to
  <strong>ZipArchive::extractTo()</strong>.

<comment>Param:</comment>
  <info>string</info>             <strong>$directory</strong>  Path to extract the given <strong>$files</strong> to
  <info>array|string|null</info>  <strong>$files</strong>      The name of a file or directory to extract, or an array of
                                 files/directories to extract, <info>null</info> to skip this param
  <info>bool</info>               <strong>$overwrite</strong>  Set to <info>true</info> to enable overwriting existing files

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>PharData::extractTo()</strong>


id: Phar::getAlias
type: function
doc:
<comment>Description:</comment>
  Get the alias for Phar
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>string|null</info>  Returns the alias or <info>null</info> if there's no alias.


id: Phar::getMetadata
type: function
doc:
<comment>Description:</comment>
  Returns phar archive meta-data
  
  Retrieve archive meta-data.  Meta-data can be any PHP variable that can be serialized.

<comment>Return:</comment>
  <info>mixed</info>  Any PHP value that can be serialized and is stored as meta-data for the Phar archive, or
         <info>null</info> if no meta-data is stored.

<comment>See Also:</comment>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::delMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>


id: Phar::getModified
type: function
doc:
<comment>Description:</comment>
  Return whether phar was modified
  
  This method can be used to determine whether a phar has either had an internal file deleted, or
  contents of a file changed in some way.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the phar has been modified since opened, <info>false</info> if not.


id: Phar::getPath
type: function
doc:
<comment>Description:</comment>
  Get the real path to the Phar archive on disk
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>string</info>  


id: Phar::getSignature
type: function
doc:
<comment>Description:</comment>
  Return MD5/SHA1/SHA256/SHA512/OpenSSL signature of a Phar archive
  
  Returns the verification signature of a phar archive in a hexadecimal string.

<comment>Return:</comment>
  <info>array|false</info>  Array with the opened archive's signature in <return>hash</return> key and <return>MD5</return>, <return>SHA-1</return>, <return>SHA-256</return>,
               <return>SHA-512</return>, or <return>OpenSSL</return> in <return>hash_type</return>.  This signature is a hash calculated on the entire
               phar's contents, and may be used to verify the integrity of the archive. A valid
               signature is absolutely required of all executable phar archives if the
               phar.require_hash INI variable is set to true. If there is no signature, the function
               returns <info>false</info>.


id: Phar::getStub
type: function
doc:
<comment>Description:</comment>
  Return the PHP loader or bootstrap stub of a Phar archive
  
  Phar archives contain a bootstrap loader, or <return>stub</return> written in PHP that is executed when the archive
  is executed in PHP either via include:  ]]> or by simple execution:

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the contents of the bootstrap loader (stub) of the current
          Phar archive.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>
   * <strong>Phar::createDefaultStub()</strong>


id: Phar::getSupportedCompression
type: function
doc:
<comment>Description:</comment>
  Return array of supported compression algorithms

<comment>Return:</comment>
  <info>array</info>  Returns an array containing any of <return>Phar::GZ</return> or <return>Phar::BZ2</return>, depending on the availability of
         the zlib extension or the bz2 extension.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::getSupportedSignatures
type: function
doc:
<comment>Description:</comment>
  Return array of supported signature types
  
  Return array of supported signature types

<comment>Return:</comment>
  <info>array</info>  Returns an array containing any of <return>MD5</return>, <return>SHA-1</return>, <return>SHA-256</return>, <return>SHA-512</return>, or <return>OpenSSL</return>.

<comment>See Also:</comment>
   * <strong>Phar::getSignature()</strong>
   * <strong>Phar::setSignatureAlgorithm()</strong>


id: Phar::getVersion
type: function
doc:
<comment>Description:</comment>
  Return version info of Phar archive
  
  Returns the API version of an opened Phar archive.

<comment>Return:</comment>
  <info>string</info>  The opened archive's API version.  This is not to be confused with the API version that
          the loaded phar extension will use to create new phars.  Each Phar archive has the API
          version hard-coded into its manifest.  See Phar file format documentation for more
          information.

<comment>See Also:</comment>
   * <strong>Phar::apiVersion()</strong>


id: Phar::hasMetadata
type: function
doc:
<comment>Description:</comment>
  Returns whether phar has global meta-data
  
  Returns whether phar has global meta-data set.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if meta-data has been set, and <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>Phar::getMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::delMetadata()</strong>


id: Phar::interceptFileFuncs
type: function
doc:
<comment>Description:</comment>
  Instructs phar to intercept fopen, file_get_contents, opendir, and all of the stat-related
  functions
  
  instructs phar to intercept <strong>fopen()</strong>, <strong>readfile()</strong>, <strong>file_get_contents()</strong>, <strong>opendir()</strong>, and all of the
  stat-related functions.  If any of these functions is called from within a phar archive with a
  relative path, the call is modified to access a file within the phar archive.  Absolute paths are
  assumed to be attempts to load external files from the filesystem.
  
  This function makes it possible to run PHP applications designed to run off of a hard disk as a
  phar application.

<comment>Return:</comment>
  <info>void</info>  


id: Phar::isBuffering
type: function
doc:
<comment>Description:</comment>
  Used to determine whether Phar write operations are being buffered, or are flushing directly to
  disk
  
  This method can be used to determine whether a Phar will save changes to disk immediately, or
  whether a call to <strong>Phar::stopBuffering()</strong> is needed to enable saving changes.
  
  Phar write buffering is per-archive, buffering active for the <return>foo.phar</return> Phar archive does not
  affect changes to the <return>bar.phar</return> Phar archive.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the write operations are being buffer, <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>Phar::startBuffering()</strong>
   * <strong>Phar::stopBuffering()</strong>


id: Phar::isCompressed
type: function
doc:
<comment>Description:</comment>
  Returns Phar::GZ or PHAR::BZ2 if the entire phar archive is compressed (.tar.gz/tar.bz and so on)
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Returns Phar::GZ or PHAR::BZ2 if the entire phar archive is compressed (.tar.gz/tar.bz and so on).
  Zip-based phar archives cannot be compressed as a file, and so this method will always return
  <info>false</info> if a zip-based phar archive is queried.

<comment>Return:</comment>
  <info>int|false</info>  <return>Phar::GZ</return>, <return>Phar::BZ2</return> or <info>false</info>.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>


id: Phar::isFileFormat
type: function
doc:
<comment>Description:</comment>
  Returns true if the phar archive is based on the tar/phar/zip file format depending on the
  parameter

<comment>Param:</comment>
  <info>int</info>  <strong>$format</strong>  Either <return>Phar::PHAR</return>, <return>Phar::TAR</return>, or <return>Phar::ZIP</return> to test for the format of the archive.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the phar archive matches the file format requested by the parameter

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>


id: Phar::isValidPharFilename
type: function
doc:
<comment>Description:</comment>
  Returns whether the given filename is a valid phar filename
  
  Returns whether the given filename is a valid phar filename that will be recognized as a phar
  archive by the phar extension.  This can be used to test a name without having to instantiate a
  phar archive and catch the inevitable Exception that will be thrown if an invalid name is
  specified.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>    The name or full path to a phar archive not yet created
  <info>bool</info>    <strong>$executable</strong>  This parameter determines whether the filename should be treated as a phar
                       executable archive, or a data non-executable archive

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the filename is valid, <info>false</info> if not.


id: Phar::isWritable
type: function
doc:
<comment>Description:</comment>
  Returns true if the phar archive can be modified
  
  This method returns <info>true</info> if <return>phar.readonly</return> is <return>0</return>, and the actual phar archive on disk is not
  read-only.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the phar archive can be modified

<comment>See Also:</comment>
   * <strong>Phar::canWrite()</strong>
   * <strong>PharData::isWritable()</strong>


id: Phar::loadPhar
type: function
doc:
<comment>Description:</comment>
  Loads any phar archive with an alias
  
  This can be used to read the contents of an external Phar archive.  This is most useful for
  assigning an alias to a phar so that subsequent references to the phar can use the shorter alias,
  or for loading Phar archives that only contain data and are not intended for execution/inclusion
  in PHP scripts.

<comment>Param:</comment>
  <info>string</info>       <strong>$filename</strong>  the full or relative path to the phar archive to open
  <info>string|null</info>  <strong>$alias</strong>     The alias that may be used to refer to the phar archive.  Note that many
                          phar archives specify an explicit alias inside the phar archive, and a
                          <class>PharException</class> will be thrown if a new alias is specified in this case.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::mapPhar()</strong>


id: Phar::mapPhar
type: function
doc:
<comment>Description:</comment>
  Reads the currently executed file (a phar) and registers its manifest
  
  This static method can only be used inside a Phar archive's loader stub in order to initialize the
  phar when it is directly executed, or when it is included in another script.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$alias</strong>   The alias that can be used in <return>phar://</return> URLs to refer to this archive, rather
                        than its full path.
  <info>int</info>          <strong>$offset</strong>  Unused variable, here for compatibility with PEAR's PHP_Archive.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::loadPhar()</strong>


id: Phar::mount
type: function
doc:
<comment>Description:</comment>
  Mount an external path or file to a virtual location within the phar archive
  
  Much like the unix file system concept of mounting external devices to paths within the directory
  tree, <strong>Phar::mount()</strong> allows referring to external files and directories as if they were inside of
  an archive.  This allows powerful abstraction such as referring to external configuration files as
  if they were inside the archive.

<comment>Param:</comment>
  <info>string</info>  <strong>$pharPath</strong>      The internal path within the phar archive to use as the mounted path
                         location. This must be a relative path within the phar archive, and must
                         not already exist.
  <info>string</info>  <strong>$externalPath</strong>  A path or URL to an external file or directory to mount within the phar
                         archive

<comment>Return:</comment>
  <info>void</info>  No return.  <class>PharException</class> is thrown on failure.


id: Phar::mungServer
type: function
doc:
<comment>Description:</comment>
  Defines a list of up to 4 $_SERVER variables that should be modified for execution
  
  <strong>Phar::mungServer()</strong> should only be called within the stub of a phar archive.
  
  Defines a list of up to 4 $_SERVER variables that should be modified for execution. Variables that
  can be modified to remove traces of phar execution are <return>REQUEST_URI</return>, <return>PHP_SELF</return>, <return>SCRIPT_NAME</return> and
  <return>SCRIPT_FILENAME</return>.
  
  On its own, this method does nothing.  Only when combined with <strong>Phar::webPhar()</strong> does it take
  effect, and only when the requested file is a PHP file to be parsed.  Note that the <return>PATH_INFO</return> and
  <return>PATH_TRANSLATED</return> variables are always modified.
  
  The original values of variables that are modified are stored in the SERVER array with <return>PHAR_</return>
  prepended, so for instance <return>SCRIPT_NAME</return> would be saved as <return>PHAR_SCRIPT_NAME</return>.

<comment>Param:</comment>
  <info>array</info>  <strong>$variables</strong>  An array of any of the strings <return>REQUEST_URI</return>, <return>PHP_SELF</return>, <return>SCRIPT_NAME</return> and
                     <return>SCRIPT_FILENAME</return>. Other values trigger an exception, and <strong>Phar::mungServer()</strong> is
                     case-sensitive.

<comment>Return:</comment>
  <info>void</info>  No return.

<comment>See Also:</comment>
   * <strong>Phar::webPhar()</strong>
   * <strong>Phar::setStub()</strong>


id: Phar::offsetExists
type: function
doc:
<comment>Description:</comment>
  Determines whether a file exists in the phar
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a Phar archive using array access brackets.
  
  offsetExists() is called whenever <strong>isset()</strong> is called.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  The filename (relative path) to look for in a Phar.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the file exists within the phar, or <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>Phar::offsetGet()</strong>
   * <strong>Phar::offsetSet()</strong>
   * <strong>Phar::offsetUnset()</strong>


id: Phar::offsetGet
type: function
doc:
<comment>Description:</comment>
  Gets a PharFileInfo object for a specific file
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a Phar archive using array access brackets. Phar::offsetGet is used  for retrieving
  files from a Phar archive.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  The filename (relative path) to look for in a Phar.

<comment>Return:</comment>
  <info>SplFileInfo</info>  A <class>PharFileInfo</class> object is returned that can be used to iterate over a file's contents
               or to retrieve information about the current file.

<comment>See Also:</comment>
   * <strong>Phar::offsetExists()</strong>
   * <strong>Phar::offsetSet()</strong>
   * <strong>Phar::offsetUnset()</strong>


id: Phar::offsetSet
type: function
doc:
<comment>Description:</comment>
  Set the contents of an internal file to those of an external file
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a Phar archive using array access brackets.  offsetSet is used for modifying an
  existing file, or adding a new file to a Phar archive.

<comment>Param:</comment>
  <info>string</info>           <strong>$localName</strong>  The filename (relative path) to modify in a Phar.
  <info>resource|string</info>  <strong>$value</strong>      Content of the file.

<comment>Return:</comment>
  <info>void</info>  No return values.

<comment>See Also:</comment>
   * <strong>Phar::offsetExists()</strong>
   * <strong>Phar::offsetGet()</strong>
   * <strong>Phar::offsetUnset()</strong>


id: Phar::offsetUnset
type: function
doc:
<comment>Description:</comment>
  Remove a file from a phar
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a Phar archive using array access brackets.  offsetUnset is used for deleting an
  existing file, and is called by the <strong>unset()</strong> language construct.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  The filename (relative path) to modify in a Phar.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::offsetExists()</strong>
   * <strong>Phar::offsetGet()</strong>
   * <strong>Phar::offsetSet()</strong>
   * <strong>Phar::unlinkArchive()</strong>
   * <strong>Phar::delete()</strong>


id: Phar::running
type: function
doc:
<comment>Description:</comment>
  Returns the full path on disk or full phar URL to the currently executing Phar archive
  
  Returns the full path to the running phar archive.  This is intended for use much like the
  <return>__FILE__</return> magic constant, and only has effect inside an executing phar archive.
  
  Inside the stub of an archive, <strong>Phar::running()</strong> returns <return>""</return>.  Simply use <info>__FILE__</info> to access the
  current running phar inside a stub.

<comment>Param:</comment>
  <info>bool</info>  <strong>$returnPhar</strong>  If <info>false</info>, the full path on disk to the phar archive is returned.  If <info>true</info>, a
                     full phar URL is returned.

<comment>Return:</comment>
  <info>string</info>  Returns the filename if valid, empty string otherwise.


id: Phar::setAlias
type: function
doc:
<comment>Description:</comment>
  Set the alias for the Phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Set the alias for the Phar archive, and write it as the permanent alias for this phar archive.  An
  alias can be used internally to a phar archive to ensure that use of the <return>phar</return> stream wrapper to
  access internal files always works regardless of the location of the phar archive on the
  filesystem.  Another alternative is to rely upon Phar's interception of <strong>include()</strong> or to use
  <strong>Phar::interceptFileFuncs()</strong> and use relative paths.

<comment>Param:</comment>
  <info>string</info>  <strong>$alias</strong>  A shorthand string that this archive can be referred to in <return>phar</return> stream wrapper
                  access.

<comment>Return:</comment>
  <info>bool</info>  

<comment>See Also:</comment>
   * <strong>Phar::__construct()</strong>
   * <strong>Phar::interceptFileFuncs()</strong>


id: Phar::setDefaultStub
type: function
doc:
<comment>Description:</comment>
  Used to set the PHP loader or bootstrap stub of a Phar archive to the default loader
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This method is a convenience method that combines the functionality of <strong>Phar::createDefaultStub()</strong>
  and <strong>Phar::setStub()</strong>.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$index</strong>     Relative path within the phar archive to run if accessed on the
                          command-line
  <info>string|null</info>  <strong>$webIndex</strong>  Relative path within the phar archive to run if accessed through a web
                          browser

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>
   * <strong>Phar::createDefaultStub()</strong>


id: Phar::setMetadata
type: function
doc:
<comment>Description:</comment>
  Sets phar archive meta-data
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  <strong>Phar::setMetadata()</strong> should be used to store customized data that describes something about the
  phar archive as a complete entity. <strong>PharFileInfo::setMetadata()</strong> should be used for file-specific
  meta-data. Meta-data can slow down the performance of loading a phar archive if the data is large.
  
  Some possible uses for meta-data include specifying which file within the archive should be used
  to bootstrap the archive, or the location of a file manifest like PEAR's package.xml file.
  However, any useful data that describes the phar archive may be stored.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$metadata</strong>  Any PHP variable containing information to store that describes the phar archive

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::getMetadata()</strong>
   * <strong>Phar::delMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>


id: Phar::setSignatureAlgorithm
type: function
doc:
<comment>Description:</comment>
  Set the signature algorithm for a phar and apply it
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  set the signature algorithm for a phar and apply it.  The signature algorithm must be one of
  <return>Phar::MD5</return>, <return>Phar::SHA1</return>, <return>Phar::SHA256</return>, <return>Phar::SHA512</return>, or <return>Phar::OPENSSL</return>.
  
  Note that all executable phar archives have a signature created automatically, <return>SHA1</return> by default.
  data tar- or zip-based archives (archives created with the <class>PharData</class> class) must have their
  signature created and set explicitly via <strong>Phar::setSignatureAlgorithm()</strong>.

<comment>Param:</comment>
  <info>int</info>          <strong>$algo</strong>        One of <return>Phar::MD5</return>, <return>Phar::SHA1</return>, <return>Phar::SHA256</return>, <return>Phar::SHA512</return>, or
                            <return>Phar::OPENSSL</return>
  <info>string|null</info>  <strong>$privateKey</strong>  The contents of an OpenSSL private key, as extracted from a certificate
                            or OpenSSL key file: setSignatureAlgorithm(Phar::OPENSSL, $pkey);
                            ?> ]]> See phar introduction for instructions on naming and placement of
                            the public key file.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::getSupportedSignatures()</strong>
   * <strong>Phar::getSignature()</strong>


id: Phar::setStub
type: function
doc:
<comment>Description:</comment>
  Used to set the PHP loader or bootstrap stub of a Phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This method is used to add a PHP bootstrap loader stub to a new Phar archive, or to replace the
  loader stub in an existing Phar archive.
  
  The loader stub for a Phar archive is used whenever an archive is included directly as in this
  example:
  
  The loader is not accessed when including a file through the <return>phar</return> stream wrapper like so:

<comment>Param:</comment>
  <info>resource|string</info>  <strong>$stub</strong>    A string or an open stream handle to use as the executable stub for this
                            phar archive.
  <info>int</info>              <strong>$length</strong>  

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::getStub()</strong>
   * <strong>Phar::createDefaultStub()</strong>


id: Phar::startBuffering
type: function
doc:
<comment>Description:</comment>
  Start buffering Phar write operations, do not modify the Phar object on disk
  
  Although technically unnecessary, the <strong>Phar::startBuffering()</strong> method can provide a significant
  performance boost when creating or modifying a Phar archive with a large number of files.
  Ordinarily, every time a file within a Phar archive is created or modified in any way, the entire
  Phar archive will be recreated with the changes.  In this way, the archive will be up-to-date with
  the activity performed on it.
  
  However, this can be unnecessary when simply creating a new Phar archive, when it would make more
  sense to write the entire archive out at once. Similarly, it is often necessary to make a series
  of changes and to ensure that they all are possible before making any changes on disk, similar to
  the relational database concept of transactions.  the <strong>Phar::startBuffering()</strong>/<strong>Phar::stopBuffering()</strong>
  pair of methods is provided for this purpose.
  
  Phar write buffering is per-archive, buffering active for the <return>foo.phar</return> Phar archive does not
  affect changes to the <return>bar.phar</return> Phar archive.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::stopBuffering()</strong>
   * <strong>Phar::isBuffering()</strong>


id: Phar::stopBuffering
type: function
doc:
<comment>Description:</comment>
  Stop buffering write requests to the Phar archive, and save changes to disk
  
  <strong>Phar::stopBuffering()</strong> is used in conjunction with the <strong>Phar::startBuffering()</strong> method.
  <strong>Phar::startBuffering()</strong> can provide a significant performance boost when creating or modifying a
  Phar archive with a large number of files.  Ordinarily, every time a file within a Phar archive is
  created or modified in any way, the entire Phar archive will be recreated with the changes.  In
  this way, the archive will be up-to-date with the activity performed on it.
  
  However, this can be unnecessary when simply creating a new Phar archive, when it would make more
  sense to write the entire archive out at once. Similarly, it is often necessary to make a series
  of changes and to ensure that they all are possible before making any changes on disk, similar to
  the relational database concept of transactions.  The <strong>Phar::startBuffering()</strong>/<strong>Phar::stopBuffering()</strong>
  pair of methods is provided for this purpose.
  
  Phar write buffering is per-archive, buffering active for the <return>foo.phar</return> Phar archive does not
  affect changes to the <return>bar.phar</return> Phar archive.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::startBuffering()</strong>
   * <strong>Phar::isBuffering()</strong>


id: Phar::unlinkArchive
type: function
doc:
<comment>Description:</comment>
  Completely remove a phar archive from disk and from memory
  
  Removes a phar archive from disk and memory.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The path on disk to the phar archive.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::delete()</strong>
   * <strong>Phar::offsetUnset()</strong>


id: Phar::webPhar
type: function
doc:
<comment>Description:</comment>
  Routes a request from a web browser to an internal file within the phar archive
  
  <strong>Phar::webPhar()</strong> serves as <strong>Phar::mapPhar()</strong> for  web-based phars.  This method parses
  $_SERVER['REQUEST_URI'] and  routes a request from a web browser to an internal file within the
  phar archive.   It simulates a web server, routing requests to the correct file, echoing the
  correct  headers and parsing PHP files as needed.  Combined with <strong>Phar::mungServer()</strong>  and
  <strong>Phar::interceptFileFuncs()</strong>, any web application can be used  unmodified from a phar archive.
  
  <strong>Phar::webPhar()</strong> should only be called from the stub of a phar archive (see here for more
  information on what a stub is).

<comment>Param:</comment>
  <info>string|null</info>    <strong>$alias</strong>               The alias that can be used in <return>phar://</return> URLs to refer to this
                                      archive, rather than its full path.
  <info>string|null</info>    <strong>$index</strong>               The location within the phar of the directory index.
  <info>string|null</info>    <strong>$fileNotFoundScript</strong>  The location of the script to run when a file is not found.
                                      This script should output the proper HTTP 404 headers.
  <info>array</info>          <strong>$mimeTypes</strong>           An array mapping additional file extensions to MIME type. If
                                      the default mapping is sufficient, pass an empty array. By
                                      default, these extensions are mapped to these MIME types:
                                      Phar::PHPS, // pass to highlight_file() 'c' => 'text/plain',
                                      'cc' => 'text/plain', 'cpp' => 'text/plain', 'c++' =>
                                      'text/plain', 'dtd' => 'text/plain', 'h' => 'text/plain',
                                      'log' => 'text/plain', 'rng' => 'text/plain', 'txt' =>
                                      'text/plain', 'xsd' => 'text/plain', 'php' => Phar::PHP, //
                                      parse as PHP 'inc' => Phar::PHP, // parse as PHP 'avi' =>
                                      'video/avi', 'bmp' => 'image/bmp', 'css' => 'text/css', 'gif'
                                      => 'image/gif', 'htm' => 'text/html', 'html' => 'text/html',
                                      'htmls' => 'text/html', 'ico' => 'image/x-ico', 'jpe' =>
                                      'image/jpeg', 'jpg' => 'image/jpeg', 'jpeg' => 'image/jpeg',
                                      'js' => 'application/x-javascript', 'midi' => 'audio/midi',
                                      'mid' => 'audio/midi', 'mod' => 'audio/mod', 'mov' =>
                                      'movie/quicktime', 'mp3' => 'audio/mp3', 'mpg' =>
                                      'video/mpeg', 'mpeg' => 'video/mpeg', 'pdf' =>
                                      'application/pdf', 'png' => 'image/png', 'swf' =>
                                      'application/shockwave-flash', 'tif' => 'image/tiff', 'tiff'
                                      => 'image/tiff', 'wav' => 'audio/wav', 'xbm' => 'image/xbm',
                                      'xml' => 'text/xml',
                                      );
                                      ?> ]]>
  <info>callable|null</info>  <strong>$rewrite</strong>             The rewrites function is passed a string as its only parameter
                                      and must return a <info>string</info> or <info>false</info>.
                                      
                                      If you are using fast-cgi or cgi then the parameter passed to
                                      the function is the value of the  $_SERVER['PATH_INFO']
                                      variable. Otherwise, the parameter passed to the function is
                                      the value of the $_SERVER['REQUEST_URI'] variable.
                                      
                                      If a string is returned it is used as the internal file path.
                                      If <info>false</info> is returned then webPhar() will send a HTTP 403
                                      Denied Code.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::mungServer()</strong>
   * <strong>Phar::interceptFileFuncs()</strong>


id: PharData
type: class
doc:
<comment>Description:</comment>
  The PharData class provides a high-level interface to accessing and creating non-executable tar
  and zip archives.  Because these archives do not contain a stub and cannot be executed by the phar
  extension, it is possible to create and manipulate regular zip and tar files using the PharData
  class even if <return>phar.readonly</return> php.ini setting is <return>1</return>.


id: PharData::__construct
type: function
doc:
<comment>Description:</comment>
  Construct a non-executable tar or zip archive object

<comment>Param:</comment>
  <info>string</info>       <strong>$filename</strong>  Path to an existing tar/zip archive or to-be-created archive
  <info>int</info>          <strong>$flags</strong>     Flags to pass to <class>Phar</class> parent class <class>RecursiveDirectoryIterator</class>.
  <info>string|null</info>  <strong>$alias</strong>     Alias with which this Phar archive should be referred to in calls to
                          stream functionality.
  <info>int</info>          <strong>$format</strong>    One of the file format constants available within the <class>Phar</class> class.


id: PharData::addEmptyDir
type: function
doc:
<comment>Description:</comment>
  Add an empty directory to the tar/zip archive
  
  With this method, an empty directory is created with path <return>dirname</return>. This method is similar to
  <strong>ZipArchive::addEmptyDir()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$directory</strong>  The name of the empty directory to create in the phar archive

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>Phar::addEmptyDir()</strong>
   * <strong>PharData::addFile()</strong>
   * <strong>PharData::addFromString()</strong>


id: PharData::addFile
type: function
doc:
<comment>Description:</comment>
  Add a file from the filesystem to the tar/zip archive
  
  With this method, any file or URL can be added to the tar/zip archive.  If the optional second
  parameter <return>localname</return> is specified, the file will be stored in the archive with that name, otherwise
  the <return>file</return> parameter is used as the path to store within the archive.  URLs must have a localname or
  an exception is thrown. This method is similar to <strong>ZipArchive::addFile()</strong>.

<comment>Param:</comment>
  <info>string</info>       <strong>$filename</strong>   Full or relative path to a file on disk to be added to the phar archive.
  <info>string|null</info>  <strong>$localName</strong>  Path that the file will be stored in the archive.

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>PharData::offsetSet()</strong>
   * <strong>Phar::addFile()</strong>
   * <strong>PharData::addFromString()</strong>
   * <strong>PharData::addEmptyDir()</strong>


id: PharData::addFromString
type: function
doc:
<comment>Description:</comment>
  Add a file from a string to the tar/zip archive
  
  With this method, any string can be added to the tar/zip archive. The file will be stored in the
  archive with <return>localname</return> as its path.  This method is similar to <strong>ZipArchive::addFromString()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  Path that the file will be stored in the archive.
  <info>string</info>  <strong>$contents</strong>   The file contents to store

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>PharData::offsetSet()</strong>
   * <strong>Phar::addFromString()</strong>
   * <strong>PharData::addFile()</strong>
   * <strong>PharData::addEmptyDir()</strong>


id: PharData::buildFromDirectory
type: function
doc:
<comment>Description:</comment>
  Construct a tar/zip archive from the files within a directory
  
  Populate a tar/zip archive from directory contents.  The optional second parameter is a regular
  expression (pcre) that is used to exclude files. Any filename that matches the regular expression
  will be included, all others will be excluded.  For more fine-grained control, use
  <strong>PharData::buildFromIterator()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$directory</strong>  The full or relative path to the directory that contains all files to add to
                      the archive.
  <info>string</info>  <strong>$pattern</strong>    An optional pcre regular expression that is used to filter the list of files.
                      Only file paths matching the regular expression will be included in the
                      archive.

<comment>Return:</comment>
  <info>array</info>  <strong>Phar::buildFromDirectory()</strong> returns an associative array mapping internal path of file to
         the full path of the file on the filesystem,  başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::buildFromDirectory()</strong>
   * <strong>PharData::buildFromIterator()</strong>


id: PharData::buildFromIterator
type: function
doc:
<comment>Description:</comment>
  Construct a tar or zip archive from an iterator
  
  Populate a tar or zip archive from an iterator.  Two styles of iterators are supported, iterators
  that map the filename within the tar/zip to the name of a file on disk, and iterators like
  DirectoryIterator that return SplFileInfo objects.  For iterators that return SplFileInfo objects,
  the second parameter is required.

<comment>Param:</comment>
  <info>Traversable</info>  <strong>$iterator</strong>       Any iterator that either associatively maps tar/zip file to location
                               or returns SplFileInfo objects
  <info>string|null</info>  <strong>$baseDirectory</strong>  For iterators that return SplFileInfo objects, the portion of each
                               file's full path to remove when adding to the tar/zip archive

<comment>Return:</comment>
  <info>array</info>  <strong>PharData::buildFromIterator()</strong> returns an associative array mapping internal path of file to
         the full path of the file on the filesystem.

<comment>See Also:</comment>
   * <strong>Phar::buildFromIterator()</strong>


id: PharData::compress
type: function
doc:
<comment>Description:</comment>
  Compresses the entire tar/zip archive using Gzip or Bzip2 compression
  
  For tar archives, this method compresses the entire archive using gzip compression or bzip2
  compression.  The resulting file can be processed with the gunzip command/bunzip command, or
  accessed directly and transparently with the Phar extension.
  
  For zip archives, this method fails with an exception. The zlib extension must be enabled to
  compress with gzip compression, the bzip2 extension must be enabled in order to compress with
  bzip2 compression.
  
  In addition, this method automatically renames the archive, appending <return>.gz</return>, <return>.bz2</return> or removing the
  extension if passed <return>Phar::NONE</return> to remove compression.  Alternatively, a file extension may be
  specified with the second parameter.

<comment>Param:</comment>
  <info>int</info>          <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                             <return>Phar::NONE</return> to remove compression.
  <info>string|null</info>  <strong>$extension</strong>    By default, the extension is <return>.tar.gz</return> or <return>.tar.bz2</return> for compressing a tar,
                             and <return>.tar</return> for decompressing.

<comment>Return:</comment>
  <info>PharData|null</info>  A <class>PharData</class> object is returned on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>Phar::compress()</strong>


id: PharData::compressFiles
type: function
doc:
<comment>Description:</comment>
  Compresses all files in the current tar/zip archive
  
  For tar-based archives, this method throws a <class>BadMethodCallException</class>, as compression of individual
  files within a tar archive is not supported by the file format.  Use <strong>PharData::compress()</strong> to
  compress an entire tar-based archive.
  
  For Zip-based archives, this method compresses all files in the archive using the specified
  compression. The zlib  or bzip2 extensions must be enabled to take advantage of this feature.  In
  addition, if any files are already compressed using bzip2/zlib compression, the respective
  extension must be enabled in order to decompress the files prior to re-compressing.

<comment>Param:</comment>
  <info>int</info>  <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                     <return>Phar::NONE</return> to remove compression.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>PharData::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>PharData::decompress()</strong>


id: PharData::convertToData
type: function
doc:
<comment>Description:</comment>
  Convert a phar archive to a non-executable tar or zip file
  
  This method is used to convert a non-executable tar or zip archive to another non-executable
  format.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class>. This method should be
  used to convert a tar archive to zip format or vice-versa.  Although it is possible to simply
  change the compression of a tar archive using this method, it is better to use the
  <strong>PharData::compress()</strong> method for logical consistency.
  
  If successful, the method creates a new archive on disk and returns a <class>PharData</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int|null</info>     <strong>$format</strong>       This should be one of <return>Phar::TAR</return> or <return>Phar::ZIP</return>.  If set to <info>null</info>, the
                             existing file format will be preserved.
  <info>int|null</info>     <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression,
                             <return>Phar::GZ</return> for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based
                             compression.
  <info>string|null</info>  <strong>$extension</strong>    This parameter is used to override the default file extension for a
                             converted archive.  Note that <return>.phar</return> cannot be used anywhere in the
                             filename for a non-executable tar or zip archive.
                             
                             If converting to a tar-based phar archive, the default extensions are
                             <return>.tar</return>, <return>.tar.gz</return>, and <return>.tar.bz2</return> depending on specified compression. For
                             zip-based archives, the default extension is <return>.zip</return>.

<comment>Return:</comment>
  <info>PharData|null</info>  The method returns a <class>PharData</class> object on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>
   * <strong>PharData::convertToExecutable()</strong>


id: PharData::convertToExecutable
type: function
doc:
<comment>Description:</comment>
  Convert a non-executable tar/zip archive to an executable phar archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  This method is used to convert a non-executable tar or zip archive to an executable phar archive.
  Any of the three executable file formats (phar, tar or zip) can be used, and whole-archive
  compression can also be performed.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class>.
  
  If successful, the method creates a new archive on disk and returns a <class>Phar</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int|null</info>     <strong>$format</strong>       This should be one of <return>Phar::PHAR</return>, <return>Phar::TAR</return>, or <return>Phar::ZIP</return>.  If set to
                             <info>null</info>, the existing file format will be preserved.
  <info>int|null</info>     <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression,
                             <return>Phar::GZ</return> for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based
                             compression.
  <info>string|null</info>  <strong>$extension</strong>    This parameter is used to override the default file extension for a
                             converted archive.  Note that all zip- and tar-based phar archives must
                             contain <return>.phar</return> in their file extension in order to be processed as a
                             phar archive.
                             
                             If converting to a phar-based archive, the default extensions are
                             <return>.phar</return>, <return>.phar.gz</return>, or <return>.phar.bz2</return> depending on the specified compression.
                             For tar-based phar archives, the default extensions are <return>.phar.tar</return>,
                             <return>.phar.tar.gz</return>, and <return>.phar.tar.bz2</return>.  For zip-based phar archives, the
                             default extension is <return>.phar.zip</return>.

<comment>Return:</comment>
  <info>Phar|null</info>  The method returns a <class>Phar</class> object on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>
   * <strong>PharData::convertToData()</strong>


id: PharData::copy
type: function
doc:
<comment>Description:</comment>
  Copy a file internal to the phar archive to another new file within the phar
  
  Copy a file internal to the tar/zip archive to another new file within the same archive. This is
  an object-oriented alternative to using <strong>copy()</strong> with the phar stream wrapper.

<comment>Param:</comment>
  <info>string</info>  <strong>$from</strong>  
  <info>string</info>  <strong>$to</strong>    

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is safer to encase method call in a try/catch block and
        assume success if no exception is thrown.


id: PharData::decompress
type: function
doc:
<comment>Description:</comment>
  Decompresses the entire Phar archive
  
  For tar-based archives, this method decompresses the entire archive.
  
  For Zip-based archives, this method fails with an exception. The zlib extension must be enabled to
  decompress an archive compressed with gzip compression, and the bzip2 extension must be enabled in
  order to decompress an archive compressed with bzip2 compression.
  
  In addition, this method automatically renames the file extension of the archive, <return>.tar</return> by default.
  Alternatively, a file extension may be specified with the <strong>$extension</strong> parameter.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$extension</strong>  For decompressing, the default file extension is <return>.tar</return>. Use this parameter
                           to specify another file extension. Be aware that only executable archives
                           can contain <return>.phar</return> in their filename.

<comment>Return:</comment>
  <info>PharData|null</info>  A <class>PharData</class> object is returned on success, or <info>null</info> on failure.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>PharData::compressFiles()</strong>
   * <strong>PharData::decompressFiles()</strong>


id: PharData::decompressFiles
type: function
doc:
<comment>Description:</comment>
  Decompresses all files in the current zip archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  For tar-based archives, this method throws a <class>BadMethodCallException</class>, as compression of individual
  files within a tar archive is not supported by the file format.  Use <strong>PharData::compress()</strong> to
  compress an entire tar-based archive.
  
  For Zip-based archives, this method decompresses all files in the archive. The zlib  or bzip2
  extensions must be enabled to take advantage of this feature if any files are compressed using
  bzip2/zlib compression.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>PharData::compressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>PharData::decompress()</strong>


id: PharData::delMetadata
type: function
doc:
<comment>Description:</comment>
  Deletes the global metadata of a zip archive
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Deletes the global metadata of the zip archive

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>Phar::delMetadata()</strong>


id: PharData::delete
type: function
doc:
<comment>Description:</comment>
  Delete a file within a tar/zip archive
  
  Delete a file within an archive.  This is the functional equivalent of calling <strong>unlink()</strong> on the
  stream wrapper equivalent, as shown in the example below.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  Path within an archive to the file to delete.

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>Phar::delete()</strong>


id: PharData::extractTo
type: function
doc:
<comment>Description:</comment>
  Extract the contents of a tar/zip archive to a directory
  
  Extract all files within a tar/zip archive to disk.  Extracted files and directories preserve
  permissions as stored in the archive.  The optional parameters allow optional control over which
  files are extracted, and whether existing files on disk can be overwritten. The second parameter
  <return>files</return> can be either the name of a file or directory to extract, or an array of names of files and
  directories to extract.  By default, this method will not overwrite existing files, the third
  parameter can be set to true to enable overwriting of files. This method is similar to
  <strong>ZipArchive::extractTo()</strong>.

<comment>Param:</comment>
  <info>string</info>             <strong>$directory</strong>  Path to extract the given <return>files</return> to
  <info>array|string|null</info>  <strong>$files</strong>      The name of a file or directory to extract, or an array of
                                 files/directories to extract
  <info>bool</info>               <strong>$overwrite</strong>  Set to <info>true</info> to enable overwriting existing files

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>Phar::extractTo()</strong>


id: PharData::isWritable
type: function
doc:
<comment>Description:</comment>
  Returns true if the tar/zip archive can be modified
  
  This method returns <info>true</info> if the tar/zip archive on disk is not read-only. Unlike
  <strong>Phar::isWritable()</strong>, data-only tar/zip archives can be modified even if <return>phar.readonly</return> is set to <return>1</return>.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the tar/zip archive can be modified

<comment>See Also:</comment>
   * <strong>Phar::canWrite()</strong>
   * <strong>Phar::isWritable()</strong>


id: PharData::offsetSet
type: function
doc:
<comment>Description:</comment>
  Set the contents of a file within the tar/zip to those of an external file or string
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a tar/zip archive using array access brackets.  offsetSet is used for modifying an
  existing file, or adding a new file to a tar/zip archive.

<comment>Param:</comment>
  <info>string</info>           <strong>$localName</strong>  The filename (relative path) to modify in a tar or zip archive.
  <info>resource|string</info>  <strong>$value</strong>      Content of the file.

<comment>Return:</comment>
  <info>void</info>  No return values.

<comment>See Also:</comment>
   * <strong>Phar::offsetSet()</strong>


id: PharData::offsetUnset
type: function
doc:
<comment>Description:</comment>
  Remove a file from a tar/zip archive
  
  This is an implementation of the ArrayAccess interface allowing direct manipulation of the
  contents of a tar/zip archive using array access brackets.  offsetUnset is used for deleting an
  existing file, and is called by the <strong>unset()</strong> language construct.

<comment>Param:</comment>
  <info>string</info>  <strong>$localName</strong>  The filename (relative path) to modify in the tar/zip archive.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::offsetUnset()</strong>


id: PharData::setAlias
type: function
doc:
<comment>Description:</comment>
  Dummy function (Phar::setAlias is not valid for PharData)
  
  Non-executable tar/zip archives cannot have an alias, so this method simply throws an exception.

<comment>Param:</comment>
  <info>string</info>  <strong>$alias</strong>  A shorthand string that this archive can be referred to in <return>phar</return> stream wrapper
                  access.  This parameter is ignored.

<comment>Return:</comment>
  <info>bool</info>  

<comment>See Also:</comment>
   * <strong>Phar::setAlias()</strong>


id: PharData::setDefaultStub
type: function
doc:
<comment>Description:</comment>
  Dummy function (Phar::setDefaultStub is not valid for PharData)
  
  Non-executable tar/zip archives cannot have a stub, so this method simply throws an exception.

<comment>Param:</comment>
  <info>string|null</info>  <strong>$index</strong>     Relative path within the phar archive to run if accessed on the
                          command-line
  <info>string|null</info>  <strong>$webIndex</strong>  Relative path within the phar archive to run if accessed through a web
                          browser

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::setDefaultStub()</strong>


id: PharData::setSignatureAlgorithm
type: function
doc:
<comment>Description:</comment>
  Set the signature algorithm for a phar and apply it
  
  <class>Phar</class> nesneleri ile çalışmak için, bu yöntem
  <return>phar.readonly</return> php.ini yönergesine <return>0</return>
  atanmış olmasını gerektirir. Aksi takdirde bir
  <class>PharException</class> istisnası oluşur.
  
  Set the signature algorithm for a phar and apply it.  The signature algorithm must be one of
  <return>Phar::MD5</return>, <return>Phar::SHA1</return>, <return>Phar::SHA256</return>, <return>Phar::SHA512</return>, or <return>Phar::OPENSSL</return>.

<comment>Param:</comment>
  <info>int</info>  <strong>$algo</strong>  One of <return>Phar::MD5</return>, <return>Phar::SHA1</return>, <return>Phar::SHA256</return>, <return>Phar::SHA512</return>, or <return>Phar::OPENSSL</return>

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Phar::getSupportedSignatures()</strong>
   * <strong>Phar::getSignature()</strong>


id: PharData::setStub
type: function
doc:
<comment>Description:</comment>
  Dummy function (Phar::setStub is not valid for PharData)
  
  Non-executable tar/zip archives cannot have a stub, so this method simply throws an exception.

<comment>Param:</comment>
  <info>string</info>  <strong>$stub</strong>  A string or an open stream handle to use as the executable stub for this phar
                 archive.  This parameter is ignored.
  <info>int</info>     <strong>$len</strong>   

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>


id: PharFileInfo
type: class
doc:
<comment>Description:</comment>
  The PharFileInfo class provides a high-level interface to the contents and attributes of a single
  file within a phar archive.


id: PharFileInfo::__construct
type: function
doc:
<comment>Description:</comment>
  Construct a Phar entry object
  
  This should not be called directly.  Instead, a PharFileInfo object is initialized by calling
  <strong>Phar::offsetGet()</strong> through array access.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The full url to retrieve a file.  If you wish to retrieve the information for
                     the file <return>my/file.php</return> from the phar <return>boo.phar</return>, the entry should be
                     <return>phar://boo.phar/my/file.php</return>.


id: PharFileInfo::chmod
type: function
doc:
<comment>Description:</comment>
  Sets file-specific permission bits
  
  <strong>PharFileInfo::chmod()</strong> allows setting of the executable file permissions bit, as well as read-only
  bits.  Writeable bits are ignored, and set at runtime based on the phar.readonly INI variable. As
  with all functionality that modifies the contents of a phar, the phar.readonly INI variable must
  be off in order to succeed if the file is within a <class>Phar</class> archive.  Files within <class>PharData</class> archives
  do not have this restriction.

<comment>Param:</comment>
  <info>int</info>  <strong>$perms</strong>  permissions (see <strong>chmod()</strong>)

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: PharFileInfo::compress
type: function
doc:
<comment>Description:</comment>
  Compresses the current Phar entry with either zlib or bzip2 compression
  
  This method compresses the file inside the Phar archive using either bzip2 compression or zlib
  compression. The bzip2 or zlib extension must be enabled to take advantage of this feature.  In
  addition, if the file is already compressed, the respective extension must be enabled in order to
  decompress the file.  As with all functionality that modifies the contents of a phar, the
  phar.readonly INI variable must be off in order to succeed if the file is within a <class>Phar</class> archive.
  Files within <class>PharData</class> archives do not have this restriction.

<comment>Param:</comment>
  <info>int</info>  <strong>$compression</strong>  Compression must be <info>Phar::GZ</info> or <info>Phar::BZ2</info>.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>


id: PharFileInfo::decompress
type: function
doc:
<comment>Description:</comment>
  Decompresses the current Phar entry within the phar
  
  This method decompresses the file inside the Phar archive. Depending on how the file is
  compressed, the bzip2 or zlib extensions must be enabled to take advantage of this feature.  As
  with all functionality that modifies the contents of a phar, the phar.readonly INI variable must
  be off in order to succeed if the file is within a <class>Phar</class> archive.  Files within <class>PharData</class> archives
  do not have this restriction.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>


id: PharFileInfo::delMetadata
type: function
doc:
<comment>Description:</comment>
  Deletes the metadata of the entry
  
  Deletes the metadata of the entry, if any.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if successful, <info>false</info> if the entry had no metadata. As with all functionality
        that modifies the contents of a phar, the phar.readonly INI variable must be off in order to
        succeed if the file is within a <class>Phar</class> archive.  Files within <class>PharData</class> archives do not have
        this restriction.

<comment>See Also:</comment>
   * <strong>PharFileInfo::setMetadata()</strong>
   * <strong>PharFileInfo::hasMetadata()</strong>
   * <strong>PharFileInfo::getMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>
   * <strong>Phar::getMetadata()</strong>


id: PharFileInfo::getCRC32
type: function
doc:
<comment>Description:</comment>
  Returns CRC32 code or throws an exception if CRC has not been verified
  
  This returns the <strong>crc32()</strong> checksum of the file within the Phar archive.

<comment>Return:</comment>
  <info>int</info>  The <strong>crc32()</strong> checksum of the file within the Phar archive.


id: PharFileInfo::getCompressedSize
type: function
doc:
<comment>Description:</comment>
  Returns the actual size of the file (with compression) inside the Phar archive
  
  This returns the size of the file within the Phar archive.  Uncompressed files will return the
  same value for getCompressedSize as they will with <strong>filesize()</strong>

<comment>Return:</comment>
  <info>int</info>  The size in bytes of the file within the Phar archive on disk.

<comment>See Also:</comment>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::compressFiles()</strong>


id: PharFileInfo::getContent
type: function
doc:
<comment>Description:</comment>
  Get the complete file contents of the entry
  
  This function behaves like <strong>file_get_contents()</strong> but for Phar.

<comment>Return:</comment>
  <info>string</info>  Returns the file contents.


id: PharFileInfo::getMetadata
type: function
doc:
<comment>Description:</comment>
  Returns file-specific meta-data saved with a file
  
  Return meta-data that was saved in the Phar archive's manifest for this file.

<comment>Return:</comment>
  <info>mixed</info>  any PHP variable that can be serialized and is stored as meta-data for the file, or <info>null</info> if
         no meta-data is stored.

<comment>See Also:</comment>
   * <strong>PharFileInfo::setMetadata()</strong>
   * <strong>PharFileInfo::hasMetadata()</strong>
   * <strong>PharFileInfo::delMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>
   * <strong>Phar::getMetadata()</strong>


id: PharFileInfo::getPharFlags
type: function
doc:
<comment>Description:</comment>
  Returns the Phar file entry flags
  
  This returns the flags set in the manifest for a Phar.  This will always return <return>0</return> in the current
  implementation.

<comment>Return:</comment>
  <info>int</info>  The Phar flags (always <return>0</return> in the current implementation)


id: PharFileInfo::hasMetadata
type: function
doc:
<comment>Description:</comment>
  Returns the metadata of the entry
  
  Returns the metadata of a file within a phar archive.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>false</info> if no metadata is set or is <info>null</info>, <info>true</info> if metadata is not <info>null</info>

<comment>See Also:</comment>
   * <strong>PharFileInfo::setMetadata()</strong>
   * <strong>PharFileInfo::getMetadata()</strong>
   * <strong>PharFileInfo::delMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>
   * <strong>Phar::getMetadata()</strong>


id: PharFileInfo::isCRCChecked
type: function
doc:
<comment>Description:</comment>
  Returns whether file entry has had its CRC verified
  
  This returns whether a file within a Phar archive has had its CRC verified.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the file has had its CRC verified, <info>false</info> if not.


id: PharFileInfo::isCompressed
type: function
doc:
<comment>Description:</comment>
  Returns whether the entry is compressed
  
  This returns whether a file is compressed within a Phar archive with either Gzip or Bzip2
  compression.

<comment>Param:</comment>
  <info>int|null</info>  <strong>$compression</strong>  One of <info>Phar::GZ</info> or <info>Phar::BZ2</info>, defaults to any compression.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the file is compressed within the Phar archive, <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::compressFiles()</strong>


id: PharFileInfo::setMetadata
type: function
doc:
<comment>Description:</comment>
  Sets file-specific meta-data saved with a file
  
  <strong>PharFileInfo::setMetadata()</strong> should only be used to store customized data in a file that cannot be
  represented with existing information stored with a file. Meta-data can significantly slow down
  the performance of loading a phar archive if the data is large, or if there are many files
  containing meta-data. It is important to note that file permissions are natively supported inside
  a phar; it is possible to set them with the <strong>PharFileInfo::chmod()</strong> method.  As with all
  functionality that modifies the contents of a phar, the phar.readonly INI variable must be off in
  order to succeed if the file is within a <class>Phar</class> archive.  Files within <class>PharData</class> archives do not have
  this restriction.
  
  Some possible uses for meta-data include passing a user/group that should be set when a file is
  extracted from the phar to disk.  Other uses could include explicitly specifying a MIME type to
  return.  However, any useful data that describes a file, but should not be contained inside of it
  may be stored.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$metadata</strong>  Any PHP variable containing information to store alongside a file

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>PharFileInfo::hasMetadata()</strong>
   * <strong>PharFileInfo::getMetadata()</strong>
   * <strong>PharFileInfo::delMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>
   * <strong>Phar::getMetadata()</strong>


id: PhpToken
type: class
doc:
<comment>Description:</comment>
  Bu sınıf, <strong>token_get_all()</strong> işlevi yerine kullanılabilir. İşlev, dizgecikleri tek karakterli bir
  dizge veya dizgecik kimliği, dizgecik metni ve satır numarasını içeren bir dizi olarak
  döndürürken, <strong>PhpToken::tokenize()</strong> tüm dizgecikleri PhpToken nesneleri içinde normalleştirir, bu da
  kodun dizgecikler üzerinde daha verimli çalışmasını ve okunabilmesini sağlar.


id: PhpToken::__construct
type: function
doc:
<comment>Description:</comment>
  Yeni bir PhpToken nesnesi döndürür
  
  Yeni bir PhpToken nesnesi döndürür.

<comment>Param:</comment>
  <info>int</info>     <strong>$kimlik</strong>     T_* sabitlerinden biri (bkz: ) veya tek karakterlik bir dizgeciği temsil eden
                      bir ASCII değer.
  <info>string</info>  <strong>$metin</strong>      Dizgeciğin metinsel gösterimi.
  <info>int</info>     <strong>$satır_num</strong>  Dizgeciğin başlangıç satır numarası (1'den başlar).
  <info>int</info>     <strong>$konum</strong>      Dizgeciğin dizge içindeki başlangıç konumu (bayt sayısı olup 0'dan başlar)

<comment>See Also:</comment>
   * <strong>PhpToken::tokenize()</strong>


id: PhpToken::__toString
type: function
doc:
<comment>Description:</comment>
  Dizgeciğin metinsel gösterimini döndürür
  
  Dizgeciğin metinsel gösterimini döndürür.

<comment>Return:</comment>
  <info>string</info>  Dizgeciğin metinsel gösterimini döndürür.

<comment>See Also:</comment>
   * <strong>token_name()</strong>


id: PhpToken::getTokenName
type: function
doc:
<comment>Description:</comment>
  Dizgeciğin ismini döndürür
  
  Dizgeciğin ismini döndürür

<comment>Return:</comment>
  <info>string|null</info>  Tek karakterlik dizgeciklerde bir ASCII karakter, bilinen dizgecikler için T_*
               sabitlerinden biri (bkz: ), veya dizgecik bilinmiyorsa <info>null</info> döner.

<comment>See Also:</comment>
   * <strong>PhpToken::tokenize()</strong>
   * <strong>token_name()</strong>


id: PhpToken::is
type: function
doc:
<comment>Description:</comment>
  Dizgecik belirtilen çeşit mi diye bakar
  
  Belirtilen <strong>$çeşit</strong> için mantıksal bir değer döndürür.

<comment>Param:</comment>
  <info>int|string|array</info>  <strong>$çeşit</strong>  Digeciğin kimliğiyle veya metin içeriğiyle eşleşecek tek bir değer veya
                            bunların bir dizisi.

<comment>Return:</comment>
  <info>bool</info>  Belirtilen çeşit için mantıksal bir değer döndürür.

<comment>See Also:</comment>
   * <strong>token_name()</strong>


id: PhpToken::isIgnorable
type: function
doc:
<comment>Description:</comment>
  Dizgeciğin PHP çözümleyicisi tarafından yoksayılabilir olup olmadığına bakar
  
  Dizgeciğin PHP çözümleyicisi tarafından yoksayılabilir olup olmadığına bağlı olarak mantıksal bir
  değer döndürür.

<comment>Return:</comment>
  <info>bool</info>  Dizgeciğin PHP çözümleyicisi tarafından yoksayılabilir (boşluklar veya açıklamalar gibi)
        olup olmadığına bağlı olarak mantıksal bir değer döndürür.

<comment>See Also:</comment>
   * <strong>PhpToken::tokenize()</strong>


id: PhpToken::tokenize
type: function
doc:
<comment>Description:</comment>
  Belirtilen kaynağı PhpToken nesneleri tarafından temsil edilen PHP dizgeciklerine böler
  
  Belirtilen <strong>$kaynak</strong> içindeki dizgeciklerin PhpToken nesnelerini içeren bir dizi döndürür.

<comment>Param:</comment>
  <info>string</info>  <strong>$kaynak</strong>      Çözümlenecek PHP kodu.
  <info>int</info>     <strong>$seçenekler</strong>  Geçerli seçenekler: <info>TOKEN_PARSE</info> - Belirli bağlamlarda dahili kullanıma
                       ayrılmış sözcükleri kullanma yeteneğini tanır.
                       
                       <info>TOKEN_PARSE</info> - Belirli bağlamlarda dahili kullanıma ayrılmış sözcükleri
                       kullanma yeteneğini tanır.

<comment>Return:</comment>
  <info>array</info>  PhpToken veya çocuk veya torunları tarafından temsil edilen bir PHP dizgecikleri dizisi
         döner. PhpToken nensnesinin sorunsuz şekilde genişletilebilmesi için yöntem <info>static[]</info> dizi
         döndürür.

<comment>See Also:</comment>
   * <strong>token_get_all()</strong>


id: Pool
type: class
doc:
<comment>Description:</comment>
  A Pool is a container for, and controller of, an adjustable number of Workers.
  
  Pooling provides a higher level abstraction of the Worker functionality, including the management
  of references in the way required by pthreads.


id: Pool::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new Pool of Workers
  
  Construct a new pool of workers. Pools lazily create their threads, which means new threads will
  only be spawned when they are required to execute tasks.

<comment>Param:</comment>
  <info>int</info>     <strong>$size</strong>   The maximum number of workers for this pool to create
  <info>string</info>  <strong>$class</strong>  The class for new Workers. If no class is given, then it defaults to the <class>Worker</class>
                  class.
  <info>array</info>   <strong>$ctor</strong>   An array of arguments to be passed to new workers' constructors


id: Pool::collect
type: function
doc:
<comment>Description:</comment>
  Collect references to completed tasks
  
  Allows the pool to collect references determined to be garbage by the optionally given collector.

<comment>Param:</comment>
  <info>Callable</info>  <strong>$collector</strong>  A Callable collector that returns a boolean on whether the task can be
                        collected or not. Only in rare cases should a custom collector need to be
                        used.

<comment>Return:</comment>
  <info>int</info>  The number of remaining tasks in the pool to be collected.


id: Pool::resize
type: function
doc:
<comment>Description:</comment>
  Resize the Pool
  
  Resize the Pool

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>  The maximum number of Workers this Pool can create

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Pool::shutdown
type: function
doc:
<comment>Description:</comment>
  Shutdown all workers
  
  Shuts down all of the workers in the pool. This will block until all submitted tasks have been
  executed.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Pool::submit
type: function
doc:
<comment>Description:</comment>
  Submits an object for execution
  
  Submit the task to the next Worker in the Pool

<comment>Param:</comment>
  <info>Threaded</info>  <strong>$task</strong>  The task for execution

<comment>Return:</comment>
  <info>int</info>  the identifier of the Worker executing the object


id: Pool::submitTo
type: function
doc:
<comment>Description:</comment>
  Submits a task to a specific worker for execution
  
  Submit a task to the specified worker in the pool. The workers are indexed from 0, and will only
  exist if the pool has needed to create them (since threads are lazily spawned).

<comment>Param:</comment>
  <info>int</info>       <strong>$worker</strong>  The worker to stack the task onto, indexed from <return>0</return>.
  <info>Threaded</info>  <strong>$task</strong>    The task for execution.

<comment>Return:</comment>
  <info>int</info>  The identifier of the worker that accepted the task.


id: QuickHashIntHash
type: class
doc:
<comment>Description:</comment>
  This class wraps around a hash containing integer numbers, where the values are also integer
  numbers. Hashes are also available as implementation of the ArrayAccess interface.
  
  Hashes can also be iterated over with <return>foreach</return> as the Iterator interface is implemented as well.
  The order of which elements are returned in is not guaranteed.


id: QuickHashIntHash::CHECK_FOR_DUPES
type: constant
doc:
<comment>Description:</comment>
  If enabled, adding duplicate elements to a set (through either QuickHashIntHash::add or
  QuickHashIntHash::loadFromFile) will result in those elements to be dropped from the set. This
  will take up extra time, so only used when it is required.


id: QuickHashIntHash::DO_NOT_USE_ZEND_ALLOC
type: constant
doc:
<comment>Description:</comment>
  Disables the use of PHP's internal memory manager for internal set structures. With this option
  enabled, internal allocations will not count towards the memory_limit settings.


id: QuickHashIntHash::HASHER_JENKINS1
type: constant
doc:
<comment>Description:</comment>
  This is the default hashing function to turn the integer hashes into bucket list indexes.


id: QuickHashIntHash::HASHER_NO_HASH
type: constant
doc:
<comment>Description:</comment>
  Selects to not use a hashing function, but merely use a modulo to find the bucket list index. This
  is not faster than normal hashing, and gives more collisions.


id: QuickHashIntHash::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new QuickHashIntHash object
  
  This constructor creates a new <class>QuickHashIntHash</class>. The size is the amount of bucket lists to create.
  The more lists there are, the less collisions you will have. Options are also supported.

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>     The amount of bucket lists to configure. The number you pass in will be
                 automatically rounded up to the next power of two. It is also automatically limited
                 from <return>64</return> to <return>4194304</return>.
  <info>int</info>  <strong>$options</strong>  The options that you can pass in are: <info>QuickHashIntHash::CHECK_FOR_DUPES</info>, which
                 makes sure no duplicate entries are added to the hash;
                 <info>QuickHashIntHash::DO_NOT_USE_ZEND_ALLOC</info> to not use PHP's internal memory manager as
                 well as one of <info>QuickHashIntHash::HASHER_NO_HASH</info>, <info>QuickHashIntHash::HASHER_JENKINS1</info>
                 or <info>QuickHashIntHash::HASHER_JENKINS2</info>. These last three configure which hashing
                 algorithm to use. All options can be combined using bitmasks.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new <class>QuickHashIntHash</class> object.


id: QuickHashIntHash::add
type: function
doc:
<comment>Description:</comment>
  This method adds a new entry to the hash
  
  This method adds a new entry to the hash, and returns whether the entry was added. Entries are by
  default always added unless <info>QuickHashIntHash::CHECK_FOR_DUPES</info> has been passed when the hash was
  created.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>    The key of the entry to add.
  <info>int</info>  <strong>$value</strong>  The optional value of the entry to add. If no value is specified, <return>1</return> will be used.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was added, and <info>false</info> if the entry was not added.


id: QuickHashIntHash::delete
type: function
doc:
<comment>Description:</comment>
  This method deletes an entry from the hash
  
  This method deletes an entry from the hash, and returns whether the entry was deleted or not.
  Associated memory structures will not be freed immediately, but rather when the hash itself is
  freed.
  
  Elements can not be deleted when the hash is used in an iterator. The method will not throw an
  exception, but simply return <info>false</info> like would happen with any other deletion failure.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to delete.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was deleted, and <info>false</info> if the entry was not deleted.


id: QuickHashIntHash::exists
type: function
doc:
<comment>Description:</comment>
  This method checks whether a key is part of the hash
  
  This method checks whether an entry with the provided key exists in the hash.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to check for whether it exists in the hash.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> when the entry was found, or <info>false</info> when the entry is not found.


id: QuickHashIntHash::get
type: function
doc:
<comment>Description:</comment>
  This method retrieves a value from the hash by its key
  
  This method retrieves a value from the hash by its key.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to retrieve.

<comment>Return:</comment>
  <info>int</info>  The value if the key exists, or <info>null</info> if the key wasn't part of the hash.


id: QuickHashIntHash::getSize
type: function
doc:
<comment>Description:</comment>
  Returns the number of elements in the hash
  
  Returns the number of elements in the hash.

<comment>Return:</comment>
  <info>int</info>  The number of elements in the hash.


id: QuickHashIntHash::loadFromFile
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a file
  
  This factory method creates a new hash from a definition file on disk. The file format consists of
  a signature <return>'QH\0x11\0'</return>, the number of elements as a 32 bit signed integer in system Endianness,
  followed by 32 bit signed integers packed together in the Endianness that the system that the code
  runs on uses. For each hash element there are two 32 bit signed integers stored. The first of each
  element is the key, and the second is the value belonging to the key. An example could be:
  
  QuickHash IntHash file format
  
  QuickHash IntHash file format

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to read the hash from.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the hash, rounded up to the nearest power of two with a maximum
                     limit of <return>4194304</return>.

<comment>Return:</comment>
  <info>QuickHashIntHash</info>  Returns a new <class>QuickHashIntHash</class>.


id: QuickHashIntHash::loadFromString
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a string
  
  This factory method creates a new hash from a definition in a string. The file format consists of
  32 bit signed integers packed together in the Endianness that the system that the code runs on
  uses. For each element there are two 32 bit signed integers stored. The first of each element is
  the key, and the second is the value belonging to the key.

<comment>Param:</comment>
  <info>string</info>  <strong>$contents</strong>  The string containing a serialized format of the hash.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the hash, rounded up to the nearest power of two with a maximum
                     limit of <return>4194304</return>.

<comment>Return:</comment>
  <info>QuickHashIntHash</info>  Returns a new <class>QuickHashIntHash</class>.


id: QuickHashIntHash::saveToFile
type: function
doc:
<comment>Description:</comment>
  This method stores an in-memory hash to disk
  
  This method stores an existing hash to a file on disk, in the same format that
  QuickHashIntHash::loadFromFile can read.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to store the hash in.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: QuickHashIntHash::saveToString
type: function
doc:
<comment>Description:</comment>
  This method returns a serialized version of the hash
  
  This method returns a serialized version of the hash in the same format that
  QuickHashIntHash::loadFromString can read.

<comment>Return:</comment>
  <info>string</info>  This method returns a string containing a serialized format of the hash. Each element is
          stored as a four byte value in the Endianness that the current system uses.


id: QuickHashIntHash::set
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value, or
    adds a new one if the entry doesn't exist
  
  This method tries to update an entry with a new value. In case the entry did not yet exist, it
  will instead add a new entry. It returns whether the entry was added or update. If there are
  duplicate keys, only the first found element will get an updated value. Use
  <info>QuickHashIntHash::CHECK_FOR_DUPES</info> during hash creation to prevent duplicate keys from being part
  of the hash.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>    The key of the entry to add or update.
  <info>int</info>  <strong>$value</strong>  The new value to set the entry with.

<comment>Return:</comment>
  <info>bool</info>  2 if the entry was found and updated, 1 if the entry was newly added or 0 if there was an
        error.


id: QuickHashIntHash::update
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value
  
  This method updates an entry with a new value, and returns whether the entry was update. If there
  are duplicate keys, only the first found element will get an updated value. Use
  <info>QuickHashIntHash::CHECK_FOR_DUPES</info> during hash creation to prevent duplicate keys from being part
  of the hash.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>    The key of the entry to update.
  <info>int</info>  <strong>$value</strong>  The new value to update the entry with.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was found and updated, and <info>false</info> if the entry was not part of the hash
        already.


id: QuickHashIntSet
type: class
doc:
<comment>Description:</comment>
  This class wraps around a set containing integer numbers.
  
  Sets can also be iterated over with <return>foreach</return> as the Iterator interface is implemented as well. The
  order of which elements are returned in is not guaranteed.


id: QuickHashIntSet::CHECK_FOR_DUPES
type: constant
doc:
<comment>Description:</comment>
  If enabled, adding duplicate elements to a set (through either QuickHashIntSet::add or
  QuickHashIntSet::loadFromFile) will result in those elements to be dropped from the set. This will
  take up extra time, so only used when it is required.


id: QuickHashIntSet::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new QuickHashIntSet object
  
  This constructor creates a new <class>QuickHashIntSet</class>. The size is the amount of bucket lists to create.
  The more lists there are, the less collisions you will have. Options are also supported.

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>     The amount of bucket lists to configure. The number you pass in will be
                 automatically rounded up to the next power of two. It is also automatically limited
                 from <return>4</return> to <return>4194304</return>.
  <info>int</info>  <strong>$options</strong>  The options that you can pass in are: <info>QuickHashIntSet::CHECK_FOR_DUPES</info>, which makes
                 sure no duplicate entries are added to the set;
                 <info>QuickHashIntSet::DO_NOT_USE_ZEND_ALLOC</info> to not use PHP's internal memory manager as
                 well as one of <info>QuickHashIntSet::HASHER_NO_HASH</info>, <info>QuickHashIntSet::HASHER_JENKINS1</info> or
                 <info>QuickHashIntSet::HASHER_JENKINS2</info>. These last three configure which hashing
                 algorithm to use. All options can be combined using bitmasks.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new <class>QuickHashIntSet</class> object.


id: QuickHashIntSet::add
type: function
doc:
<comment>Description:</comment>
  This method adds a new entry to the set
  
  This method adds a new entry to the set, and returns whether the entry was added. Entries are by
  default always added unless <info>QuickHashIntSet::CHECK_FOR_DUPES</info> has been passed when the set was
  created.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to add.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was added, and <info>false</info> if the entry was not added.


id: QuickHashIntSet::delete
type: function
doc:
<comment>Description:</comment>
  This method deletes an entry from the set
  
  This method deletes an entry from the set, and returns whether the entry was deleted or not.
  Associated memory structures will not be freed immediately, but rather when the set itself is
  freed.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to delete.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was deleted, and <info>false</info> if the entry was not deleted.


id: QuickHashIntSet::exists
type: function
doc:
<comment>Description:</comment>
  This method checks whether a key is part of the set
  
  This method checks whether an entry with the provided key exists in the set.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to check for whether it exists in the set.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> when the entry was found, or <info>false</info> when the entry is not found.


id: QuickHashIntSet::getSize
type: function
doc:
<comment>Description:</comment>
  Returns the number of elements in the set
  
  Returns the number of elements in the set.

<comment>Return:</comment>
  <info>int</info>  The number of elements in the set.


id: QuickHashIntSet::loadFromFile
type: function
doc:
<comment>Description:</comment>
  This factory method creates a set from a file
  
  This factory method creates a new set from a definition file on disk. The file format consists of
  32 bit signed integers packed together in the Endianness that the system that the code runs on
  uses.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to read the set from.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from <return>4</return> to <return>4194304</return>.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the set, rounded up to the nearest power of two with a maximum limit
                     of <return>4194304</return>.

<comment>Return:</comment>
  <info>QuickHashIntSet</info>  Returns a new <class>QuickHashIntSet</class>.


id: QuickHashIntSet::loadFromString
type: function
doc:
<comment>Description:</comment>
  This factory method creates a set from a string
  
  This factory method creates a new set from a definition in a string. The file format consists of
  32 bit signed integers packed together in the Endianness that the system that the code runs on
  uses.

<comment>Param:</comment>
  <info>string</info>  <strong>$contents</strong>  The string containing a serialized format of the set.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from <return>4</return> to <return>4194304</return>.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the set, rounded up to the nearest power of two automatically
                     limited from <return>64</return> to <return>4194304</return>.

<comment>Return:</comment>
  <info>QuickHashIntSet</info>  Returns a new <class>QuickHashIntSet</class>.


id: QuickHashIntSet::saveToFile
type: function
doc:
<comment>Description:</comment>
  This method stores an in-memory set to disk
  
  This method stores an existing set to a file on disk, in the same format that
  QuickHashIntSet::loadFromFile can read.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to store the hash in.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: QuickHashIntSet::saveToString
type: function
doc:
<comment>Description:</comment>
  This method returns a serialized version of the set
  
  This method returns a serialized version of the set in the same format that
  QuickHashIntSet::loadFromString can read.

<comment>Return:</comment>
  <info>string</info>  This method returns a string containing a serialized format of the set. Each element is
          stored as a four byte value in the Endianness that the current system uses.


id: QuickHashIntStringHash
type: class
doc:
<comment>Description:</comment>
  This class wraps around a hash containing integer numbers, where the values are strings. Hashes
  are also available as implementation of the ArrayAccess interface.
  
  Hashes can also be iterated over with <return>foreach</return> as the Iterator interface is implemented as well.
  The order of which elements are returned in is not guaranteed.


id: QuickHashIntStringHash::CHECK_FOR_DUPES
type: constant
doc:
<comment>Description:</comment>
  If enabled, adding duplicate elements to a set (through either QuickHashIntStringHash::add or
  QuickHashIntStringHash::loadFromFile) will result in those elements to be dropped from the set.
  This will take up extra time, so only used when it is required.


id: QuickHashIntStringHash::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new QuickHashIntStringHash object
  
  This constructor creates a new <class>QuickHashIntStringHash</class>. The size is the amount of bucket lists to
  create. The more lists there are, the less collisions you will have. Options are also supported.

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>     The amount of bucket lists to configure. The number you pass in will be
                 automatically rounded up to the next power of two. It is also automatically limited
                 from <return>64</return> to <return>4194304</return>.
  <info>int</info>  <strong>$options</strong>  The options that you can pass in are: <info>QuickHashIntStringHash::CHECK_FOR_DUPES</info>,
                 which makes sure no duplicate entries are added to the hash;
                 <info>QuickHashIntStringHash::DO_NOT_USE_ZEND_ALLOC</info> to not use PHP's internal memory
                 manager as well as one of <info>QuickHashIntStringHash::HASHER_NO_HASH</info>,
                 <info>QuickHashIntStringHash::HASHER_JENKINS1</info> or <info>QuickHashIntStringHash::HASHER_JENKINS2</info>.
                 These last three configure which hashing algorithm to use. All options can be
                 combined using bitmasks.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new <class>QuickHashIntStringHash</class> object.


id: QuickHashIntStringHash::add
type: function
doc:
<comment>Description:</comment>
  This method adds a new entry to the hash
  
  This method adds a new entry to the hash, and returns whether the entry was added. Entries are by
  default always added unless <info>QuickHashIntStringHash::CHECK_FOR_DUPES</info> has been passed when the hash
  was created.

<comment>Param:</comment>
  <info>int</info>     <strong>$key</strong>    The key of the entry to add.
  <info>string</info>  <strong>$value</strong>  The value of the entry to add. If a non-string is passed, it will be converted to
                  a string automatically if possible.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was added, and <info>false</info> if the entry was not added.


id: QuickHashIntStringHash::get
type: function
doc:
<comment>Description:</comment>
  This method retrieves a value from the hash by its key
  
  This method retrieves a value from the hash by its key.

<comment>Param:</comment>
  <info>int</info>  <strong>$key</strong>  The key of the entry to retrieve.

<comment>Return:</comment>
  <info>mixed</info>  The value if the key exists, or <info>null</info> if the key wasn't part of the hash.


id: QuickHashIntStringHash::loadFromFile
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a file
  
  This factory method creates a new hash from a definition file on disk. The file format consists of
  a signature <return>'QH\0x12\0'</return>, the number of elements as a 32 bit signed integer in system Endianness,
  an unsigned 32 bit integer containing the number of element data to follow in characters. This
  element data contains all the strings. After the header and the strings, the elements follow in
  pairs of two unsigned 32 bit integers where the first one is the key, and the second one the index
  in the element data string. An example could be:
  
  QuickHash IntString file format
  
  QuickHash IntString file format

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to read the hash from.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from <return>4</return> to <return>4194304</return>.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the hash, rounded up to the nearest power of two with a maximum
                     limit of <return>4194304</return>.

<comment>Return:</comment>
  <info>QuickHashIntStringHash</info>  Returns a new <class>QuickHashIntStringHash</class>.


id: QuickHashIntStringHash::loadFromString
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a string
  
  This factory method creates a new hash from a definition in a string. The format is the same as
  the one used in "loadFromFile".

<comment>Param:</comment>
  <info>string</info>  <strong>$contents</strong>  The string containing a serialized format of the hash.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from 4 to 4194304.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the hash, rounded up to the nearest power of two with a maximum
                     limit of 4194304.

<comment>Return:</comment>
  <info>QuickHashIntStringHash</info>  Returns a new QuickHashIntStringHash.


id: QuickHashIntStringHash::saveToFile
type: function
doc:
<comment>Description:</comment>
  This method stores an in-memory hash to disk
  
  This method stores an existing hash to a file on disk, in the same format that loadFromFile() can
  read.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to store the hash in.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: QuickHashIntStringHash::saveToString
type: function
doc:
<comment>Description:</comment>
  This method returns a serialized version of the hash
  
  This method returns a serialized version of the hash in the same format that
  QuickHashIntStringHash::loadFromString can read.

<comment>Return:</comment>
  <info>string</info>  This method returns a string containing a serialized format of the hash. Each element is
          stored as a four byte value in the Endianness that the current system uses.


id: QuickHashIntStringHash::set
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value, or
    adds a new one if the entry doesn't exist
  
  This method tries to update an entry with a new value. In case the entry did not yet exist, it
  will instead add a new entry. It returns whether the entry was added or update. If there are
  duplicate keys, only the first found element will get an updated value. Use
  QuickHashIntStringHash::CHECK_FOR_DUPES during hash creation to prevent duplicate keys from being
  part of the hash.

<comment>Param:</comment>
  <info>int</info>     <strong>$key</strong>    The key of the entry to add or update.
  <info>string</info>  <strong>$value</strong>  The value of the entry to add. If a non-string is passed, it will be converted to
                  a string automatically if possible.

<comment>Return:</comment>
  <info>int</info>  2 if the entry was found and updated, 1 if the entry was newly added or 0 if there was an
       error.


id: QuickHashIntStringHash::update
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value
  
  This method updates an entry with a new value, and returns whether the entry was update. If there
  are duplicate keys, only the first found element will get an updated value. Use
  QuickHashIntStringHash::CHECK_FOR_DUPES during hash creation to prevent duplicate keys from being
  part of the hash.

<comment>Param:</comment>
  <info>int</info>     <strong>$key</strong>    The key of the entry to update.
  <info>string</info>  <strong>$value</strong>  The new value for the entry. If a non-string is passed, it will be converted to a
                  string automatically if possible.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was found and updated, and <info>false</info> if the entry was not part of the hash
        already.


id: QuickHashStringIntHash
type: class
doc:
<comment>Description:</comment>
  This class wraps around a hash containing strings, where the values are integer numbers. Hashes
  are also available as implementation of the ArrayAccess interface.
  
  Hashes can also be iterated over with <return>foreach</return> as the Iterator interface is implemented as well.
  The order of which elements are returned in is not guaranteed.


id: QuickHashStringIntHash::CHECK_FOR_DUPES
type: constant
doc:
<comment>Description:</comment>
  If enabled, adding duplicate elements to a set (through either QuickHashStringIntHash::add or
  QuickHashStringIntHash::loadFromFile) will result in those elements to be dropped from the set.
  This will take up extra time, so only used when it is required.


id: QuickHashStringIntHash::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new QuickHashStringIntHash object
  
  This constructor creates a new <class>QuickHashStringIntHash</class>. The size is the amount of bucket lists to
  create. The more lists there are, the less collisions you will have. Options are also supported.

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>     The amount of bucket lists to configure. The number you pass in will be
                 automatically rounded up to the next power of two. It is also automatically limited
                 from <return>64</return> to <return>4194304</return>.
  <info>int</info>  <strong>$options</strong>  The options that you can pass in are: <info>QuickHashStringIntHash::CHECK_FOR_DUPES</info>,
                 which makes sure no duplicate entries are added to the hash and
                 <info>QuickHashStringIntHash::DO_NOT_USE_ZEND_ALLOC</info> to not use PHP's internal memory
                 manager.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new <class>QuickHashStringIntHash</class> object.


id: QuickHashStringIntHash::add
type: function
doc:
<comment>Description:</comment>
  This method adds a new entry to the hash
  
  This method adds a new entry to the hash, and returns whether the entry was added. Entries are by
  default always added unless <info>QuickHashStringIntHash::CHECK_FOR_DUPES</info> has been passed when the hash
  was created.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>    The key of the entry to add.
  <info>int</info>     <strong>$value</strong>  The value of the entry to add.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was added, and <info>false</info> if the entry was not added.


id: QuickHashStringIntHash::delete
type: function
doc:
<comment>Description:</comment>
  This method deletes an entry from the hash
  
  This method deletes an entry from the hash, and returns whether the entry was deleted or not.
  Associated memory structures will not be freed immediately, but rather when the hash itself is
  freed.
  
  Elements can not be deleted when the hash is used in an iterator. The method will not throw an
  exception, but simply return <info>false</info> like would happen with any other deletion failure.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>  The key of the entry to delete.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was deleted, and <info>false</info> if the entry was not deleted.


id: QuickHashStringIntHash::exists
type: function
doc:
<comment>Description:</comment>
  This method checks whether a key is part of the hash
  
  This method checks whether an entry with the provided key exists in the hash.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>  The key of the entry to check for whether it exists in the hash.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> when the entry was found, or <info>false</info> when the entry is not found.


id: QuickHashStringIntHash::get
type: function
doc:
<comment>Description:</comment>
  This method retrieves a value from the hash by its key
  
  This method retrieves a value from the hash by its key.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>  The key of the entry to retrieve.

<comment>Return:</comment>
  <info>mixed</info>  The value if the key exists, or <info>null</info> if the key wasn't part of the hash.


id: QuickHashStringIntHash::loadFromFile
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a file
  
  This factory method creates a new hash from a definition file on disk. The file format consists of
  a signature <return>'QH\0x21\0'</return>, the number of elements as a 32 bit signed integer in system Endianness,
  an unsigned 32 bit integer containing the number of element data to follow in characters. This
  element data contains all the strings. The follows another signed 32 bit integer containing the
  number of bucket lists.  After the header and the strings, the elements follow. They are ordered
  by bucket list so that the keys don't have to be hashed in order to restore the hash. For each
  bucket list, the following information is stored (all as 32 bit integers): the bucket list index,
  the number of elements in that list, and then in pairs of two unsigned 32 bit integers the
  elements, where the first one is the index into the string list containing the keys, and the
  second one the value.  An example could be:
  
  QuickHash StringIntHash file format
  
  QuickHash IntHash file format

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The filename of the file to read the hash from.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from <return>4</return> to <return>4194304</return>.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is read from the file format (unlike the <class>QuickHashIntHash</class> and
                     <class>QuickHashIntStringHash</class> classes, where it is automatically calculated from the
                     number of entries in the hash.)

<comment>Return:</comment>
  <info>QuickHashStringIntHash</info>  Returns a new <class>QuickHashStringIntHash</class>.


id: QuickHashStringIntHash::loadFromString
type: function
doc:
<comment>Description:</comment>
  This factory method creates a hash from a string
  
  This factory method creates a new hash from a definition in a string. The format is the same as
  the one used in "loadFromFile".

<comment>Param:</comment>
  <info>string</info>  <strong>$contents</strong>  The string containing a serialized format of the hash.
  <info>int</info>     <strong>$size</strong>      The amount of bucket lists to configure. The number you pass in will be
                     automatically rounded up to the next power of two. It is also automatically
                     limited from 4 to 4194304.
  <info>int</info>     <strong>$options</strong>   The same options that the class' constructor takes; except that the size option
                     is ignored. It is automatically calculated to be the same as the number of
                     entries in the hash, rounded up to the nearest power of two with a maximum
                     limit of 4194304.

<comment>Return:</comment>
  <info>QuickHashStringIntHash</info>  Returns a new QuickHashStringIntHash.


id: QuickHashStringIntHash::saveToString
type: function
doc:
<comment>Description:</comment>
  This method returns a serialized version of the hash
  
  This method returns a serialized version of the hash in the same format that
  QuickHashStringIntHash::loadFromString can read.

<comment>Return:</comment>
  <info>string</info>  This method returns a serialized format of an existing hash, in the same format that
          QuickHashStringIntHash::loadFromString can read.


id: QuickHashStringIntHash::set
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value, or
    adds a new one if the entry doesn't exist
  
  This method tries to update an entry with a new value. In case the entry did not yet exist, it
  will instead add a new entry. It returns whether the entry was added or update. If there are
  duplicate keys, only the first found element will get an updated value. Use
  QuickHashStringIntHash::CHECK_FOR_DUPES during hash creation to prevent duplicate keys from being
  part of the hash.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>    The key of the entry to add or update.
  <info>int</info>     <strong>$value</strong>  The value of the entry to add. If a non-string is passed, it will be converted to
                  a string automatically if possible.

<comment>Return:</comment>
  <info>int</info>  2 if the entry was found and updated, 1 if the entry was newly added or 0 if there was an
       error.


id: QuickHashStringIntHash::update
type: function
doc:
<comment>Description:</comment>
  This method updates an entry in the hash with a new value
  
  This method updates an entry with a new value, and returns whether the entry was update. If there
  are duplicate keys, only the first found element will get an updated value. Use
  QuickHashStringIntHash::CHECK_FOR_DUPES during hash creation to prevent duplicate keys from being
  part of the hash.

<comment>Param:</comment>
  <info>string</info>  <strong>$key</strong>    The key of the entry to update.
  <info>int</info>     <strong>$value</strong>  The new value for the entry. If a non-string is passed, it will be converted to a
                  string automatically if possible.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> when the entry was found and updated, and <info>false</info> if the entry was not part of the hash
        already.


id: RADIUS_ACCESS_ACCEPT
type: constant
doc:
<comment>Description:</comment>
  An Access-Accept response to an Access-Request indicating that the RADIUS server authenticated the
  user successfully.


id: RADIUS_ACCESS_CHALLENGE
type: constant
doc:
<comment>Description:</comment>
  An Access-Challenge response to an Access-Request indicating that the RADIUS server requires
  further information in another Access-Request before authenticating the user.


id: RADIUS_ACCESS_REJECT
type: constant
doc:
<comment>Description:</comment>
  An Access-Reject response to an Access-Request indicating that the RADIUS server could not
  authenticate the user.


id: RADIUS_ACCESS_REQUEST
type: constant
doc:
<comment>Description:</comment>
  An Access-Request, used to authenticate a user against a RADIUS server. Access request packets
  must include a <info>RADIUS_NAS_IP_ADDRESS</info> or a <info>RADIUS_NAS_IDENTIFIER</info> attribute, must also include a
  <info>RADIUS_USER_PASSWORD</info>, <info>RADIUS_CHAP_PASSWORD</info> or a <info>RADIUS_STATE</info> attribute, and should include a
  <info>RADIUS_USER_NAME</info> attribute.


id: RADIUS_ACCOUNTING_REQUEST
type: constant
doc:
<comment>Description:</comment>
  An Accounting-Request, used to convey accounting information for a service to the RADIUS server.


id: RADIUS_ACCT_AUTHENTIC
type: constant
doc:
<comment>Description:</comment>
  Accounting authentic, one of: <info>RADIUS_AUTH_RADIUS</info><info>RADIUS_AUTH_LOCAL</info><info>RADIUS_AUTH_REMOTE</info>


id: RADIUS_ACCT_STATUS_TYPE
type: constant
doc:
<comment>Description:</comment>
  Accounting status type, one of: <info>RADIUS_START</info><info>RADIUS_STOP</info><info>RADIUS_ACCOUNTING_ON</info><info>RADIUS_ACCOUNTING_OFF</info>


id: RADIUS_ACCT_TERMINATE_CAUSE
type: constant
doc:
<comment>Description:</comment>
  Accounting terminate cause, one of:
  <info>RADIUS_TERM_USER_REQUEST</info><info>RADIUS_TERM_LOST_CARRIER</info><info>RADIUS_TERM_LOST_SERVICE</info><info>RADIUS_TERM_IDLE_TIMEOUT</info><info>RADIUS_TERM_SESSION_TIMEOUT</info><info>RADIUS_TERM_ADMIN_RESET</info><info>RADIUS_TERM_ADMIN_REBOOT</info><info>RADIUS_TERM_PORT_ERROR</info><info>RADIUS_TERM_NAS_ERROR</info><info>RADIUS_TERM_NAS_REQUEST</info><info>RADIUS_TERM_NAS_REBOOT</info><info>RADIUS_TERM_PORT_UNNEEDED</info><info>RADIUS_TERM_PORT_PREEMPTED</info><info>RADIUS_TERM_PORT_SUSPENDED</info><info>RADIUS_TERM_SERVICE_UNAVAILABLE</info><info>RADIUS_TERM_CALLBACK</info><info>RADIUS_TERM_USER_ERROR</info><info>RADIUS_TERM_HOST_REQUEST</info>


id: RADIUS_CALLBACK_ID
type: constant
doc:
<comment>Description:</comment>
  The Callback-Id attribute. The attribute value is a <info>string</info> containing an implementation-specific
  name of the place to be called.


id: RADIUS_CALLBACK_NUMBER
type: constant
doc:
<comment>Description:</comment>
  The Callback-Number attribute. The attribute value is a <info>string</info> containing the dialing string to
  use for callback.


id: RADIUS_CHAP_PASSWORD
type: constant
doc:
<comment>Description:</comment>
  The Chap-Password attribute. The attribute value is expected to be a <info>string</info> with the first byte
  containing the CHAP identifier, and the subsequent 16 bytes containing the MD5 hash of the CHAP
  identifier, the plaintext password and the CHAP challenge value concatenated together. Note that
  the CHAP challenge value should also be sent separately in a <info>RADIUS_CHAP_CHALLENGE</info> attribute.
  
  Using CHAP passwords


id: RADIUS_CLASS
type: constant
doc:
<comment>Description:</comment>
  The Class attribute. The attribute value is an arbitrary <info>string</info> included in an Access-Accept
  message that should then be sent to the accounting server in Accounting-Request messages, and can
  be set using <strong>radius_put_attr()</strong>.


id: RADIUS_COA_ACK
type: constant
doc:
<comment>Description:</comment>
  A CoA-ACK, sent to the RADIUS server to indicate that the user authorisations have been updated.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_COA_NAK
type: constant
doc:
<comment>Description:</comment>
  A CoA-NAK, sent to the RADIUS server to indicate that the user authorisations could not be
  updated.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_COA_REQUEST
type: constant
doc:
<comment>Description:</comment>
  A CoA-Request, sent from the RADIUS server to indicate that the authorisations within the user
  session have changed. A response must be sent in the form of a CoA-ACK or a CoA-NAK.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_DISCONNECT_ACK
type: constant
doc:
<comment>Description:</comment>
  A Disconnect-ACK, sent to the RADIUS server to indicate that the user session has been terminated.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_DISCONNECT_NAK
type: constant
doc:
<comment>Description:</comment>
  A Disconnect-NAK, sent to the RADIUS server to indicate that the user session could not be
  terminated.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_DISCONNECT_REQUEST
type: constant
doc:
<comment>Description:</comment>
  A Disconnect-Request, sent from the RADIUS server to indicate that the user session must be
  terminated.
  
  This constant is available in PECL radius 1.3.0 and later.


id: RADIUS_FILTER_ID
type: constant
doc:
<comment>Description:</comment>
  The Filter-ID attribute. The attribute value is expected to be an implementation-specific,
  human-readable <info>string</info> of filters, which can be set using <strong>radius_put_attr()</strong>.


id: RADIUS_FRAMED_COMPRESSION
type: constant
doc:
<comment>Description:</comment>
  The Framed-Compression attribute. The attribute value is expected to be an <info>int</info> indicating the
  compression protocol to be used, and can be set using <strong>radius_put_int()</strong>. Possible values include
  these constants: <info>RADIUS_COMP_NONE</info>: No compression<info>RADIUS_COMP_VJ</info>: VJ TCP/IP header
  compression<info>RADIUS_COMP_IPXHDR</info>: IPX header compression<info>RADIUS_COMP_STAC_LZS</info>: Stac-LZS compression
  (added in PECL radius 1.3.0b2)


id: RADIUS_FRAMED_IPX_NETWORK
type: constant
doc:
<comment>Description:</comment>
  The Framed-IPX-Network attribute. The attribute value is an <info>int</info> containing the IPX network to be
  configured for the user, or <return>0xFFFFFFFE</return> to indicate that the RADIUS client should select the
  network, and can be accessed via <strong>radius_cvt_int()</strong>.


id: RADIUS_FRAMED_IP_ADDRESS
type: constant
doc:
<comment>Description:</comment>
  The Framed-IP-Address attribute. The attribute value is expected to be the address of the user's
  network encoded as an <info>int</info>, which can be set using <strong>radius_put_addr()</strong> and retrieved using
  <strong>radius_cvt_addr()</strong>.


id: RADIUS_FRAMED_IP_NETMASK
type: constant
doc:
<comment>Description:</comment>
  The Framed-IP-Netmask attribute. The attribute value is expected to be the netmask of the user's
  network encoded as an <info>int</info>, which can be set using <strong>radius_put_addr()</strong> and retrieved using
  <strong>radius_cvt_addr()</strong>.


id: RADIUS_FRAMED_MTU
type: constant
doc:
<comment>Description:</comment>
  The Framed-MTU attribute. The attribute value is expected to be an <info>int</info> indicating the MTU to be
  configured for the user, and can be set using <strong>radius_put_int()</strong>.


id: RADIUS_FRAMED_PROTOCOL
type: constant
doc:
<comment>Description:</comment>
  The Framed-Protocol attribute. The attribute value is expected to be an <info>int</info> indicating the framing
  to be used for framed access, and can be set using <strong>radius_put_int()</strong>. The possible attribute values
  include these constants: <info>RADIUS_PPP</info><info>RADIUS_SLIP</info><info>RADIUS_ARAP</info><info>RADIUS_GANDALF</info><info>RADIUS_XYLOGICS</info>


id: RADIUS_FRAMED_ROUTE
type: constant
doc:
<comment>Description:</comment>
  The Framed-Route attribute. The attribute value is a <info>string</info> containing an implementation-specific
  set of routes to be configured for the user.


id: RADIUS_FRAMED_ROUTING
type: constant
doc:
<comment>Description:</comment>
  The Framed-Routing attribute. The attribute value is expected to be an <info>int</info> indicating the routing
  method for the user, which can be set using <strong>radius_put_int()</strong>.
  
  Possible values include: <return>0</return>: No routing<return>1</return>: Send routing packets<return>2</return>: Listen for routing packets<return>3</return>: Send
  and listen


id: RADIUS_LOGIN_IP_HOST
type: constant
doc:
<comment>Description:</comment>
  The Login-IP-Host attribute. The attribute value is expected to the IP address to connect the user
  to, encoded as an <info>int</info>, which can be set using <strong>radius_put_addr()</strong>.


id: RADIUS_LOGIN_SERVICE
type: constant
doc:
<comment>Description:</comment>
  The Login-Service attribute. The attribute value is an <info>int</info> indicating the service to connect the
  user to on the login host. The value can be converted to a PHP integer via <strong>radius_cvt_int()</strong>.


id: RADIUS_LOGIN_TCP_PORT
type: constant
doc:
<comment>Description:</comment>
  The Login-TCP-Port attribute. The attribute value is an <info>int</info> indicating the port to connect the
  user to on the login host. The value can be converted to a PHP integer via <strong>radius_cvt_int()</strong>.


id: RADIUS_NAS_IP_ADDRESS
type: constant
doc:
<comment>Description:</comment>
  The NAS-IP-Address attribute. The attribute value is expected to the IP address of the RADIUS
  client encoded as an <info>int</info>, which can be set using <strong>radius_put_addr()</strong>.


id: RADIUS_NAS_PORT
type: constant
doc:
<comment>Description:</comment>
  The NAS-Port attribute. The attribute value is expected to be the physical port of the user on the
  RADIUS client encoded as an <info>int</info>, which can be set using <strong>radius_put_int()</strong>.


id: RADIUS_NAS_PORT_TYPE
type: constant
doc:
<comment>Description:</comment>
  NAS port type, one of:
  <info>RADIUS_ASYNC</info><info>RADIUS_SYNC</info><info>RADIUS_ISDN_SYNC</info><info>RADIUS_ISDN_ASYNC_V120</info><info>RADIUS_ISDN_ASYNC_V110</info><info>RADIUS_VIRTUAL</info><info>RADIUS_PIAFS</info><info>RADIUS_HDLC_CLEAR_CHANNEL</info><info>RADIUS_X_25</info><info>RADIUS_X_75</info><info>RADIUS_G_3_FAX</info><info>RADIUS_SDSL</info><info>RADIUS_ADSL_CAP</info><info>RADIUS_ADSL_DMT</info><info>RADIUS_IDSL</info><info>RADIUS_ETHERNET</info><info>RADIUS_XDSL</info><info>RADIUS_CABLE</info><info>RADIUS_WIRELESS_OTHER</info><info>RADIUS_WIRELESS_IEEE_802_11</info>


id: RADIUS_OPTION_SALT
type: constant
doc:
<comment>Description:</comment>
  When set, this option will result in the attribute value being salt-encrypted.


id: RADIUS_OPTION_TAGGED
type: constant
doc:
<comment>Description:</comment>
  When set, this option will result in the attribute value being tagged with the value of the tag
  parameter.


id: RADIUS_REPLY_MESSAGE
type: constant
doc:
<comment>Description:</comment>
  The Reply-Message attribute. The attribute value is a <info>string</info> containing text that may be displayed
  to the user in response to an access request.


id: RADIUS_SERVICE_TYPE
type: constant
doc:
<comment>Description:</comment>
  The Service-Type attribute. The attribute value indicates the service type the user is requesting,
  and is expected to be an <info>int</info>, which can be set using <strong>radius_put_int()</strong>.
  
  A number of constants are provided to represent the possible values of this attribute. They
  include:
  <info>RADIUS_LOGIN</info><info>RADIUS_FRAMED</info><info>RADIUS_CALLBACK_LOGIN</info><info>RADIUS_CALLBACK_FRAMED</info><info>RADIUS_OUTBOUND</info><info>RADIUS_ADMINISTRATIVE</info><info>RADIUS_NAS_PROMPT</info><info>RADIUS_AUTHENTICATE_ONLY</info><info>RADIUS_CALLBACK_NAS_PROMPT</info>


id: RADIUS_STATE
type: constant
doc:
<comment>Description:</comment>
  The State attribute. The attribute value is an implementation-defined <info>string</info> included in an
  Access-Challenge from a server that must be included in the subsequent Access-Request, and can be
  set using <strong>radius_put_attr()</strong>.


id: RADIUS_USER_NAME
type: constant
doc:
<comment>Description:</comment>
  The User-Name attribute. The attribute value is expected to be a <info>string</info> containing the name of the
  user being authenticated, and can be set using <strong>radius_put_attr()</strong>.


id: RADIUS_USER_PASSWORD
type: constant
doc:
<comment>Description:</comment>
  The User-Password attribute. The attribute value is expected to be a <info>string</info> containing the user's
  password, and can be set using <strong>radius_put_attr()</strong>. This value will be obfuscated on transmission as
  described in section 5.2 of RFC 2865.


id: RADIUS_VENDOR_MICROSOFT
type: constant
doc:
<comment>Description:</comment>
  Microsoft specific vendor attributes (RFC 2548), one of:
  <info>RADIUS_MICROSOFT_MS_CHAP_RESPONSE</info><info>RADIUS_MICROSOFT_MS_CHAP_ERROR</info><info>RADIUS_MICROSOFT_MS_CHAP_PW_1</info><info>RADIUS_MICROSOFT_MS_CHAP_PW_2</info><info>RADIUS_MICROSOFT_MS_CHAP_LM_ENC_PW</info><info>RADIUS_MICROSOFT_MS_CHAP_NT_ENC_PW</info><info>RADIUS_MICROSOFT_MS_MPPE_ENCRYPTION_POLICY</info><info>RADIUS_MICROSOFT_MS_MPPE_ENCRYPTION_TYPES</info><info>RADIUS_MICROSOFT_MS_RAS_VENDOR</info><info>RADIUS_MICROSOFT_MS_CHAP_DOMAIN</info><info>RADIUS_MICROSOFT_MS_CHAP_CHALLENGE</info><info>RADIUS_MICROSOFT_MS_CHAP_MPPE_KEYS</info><info>RADIUS_MICROSOFT_MS_BAP_USAGE</info><info>RADIUS_MICROSOFT_MS_LINK_UTILIZATION_THRESHOLD</info><info>RADIUS_MICROSOFT_MS_LINK_DROP_TIME_LIMIT</info><info>RADIUS_MICROSOFT_MS_MPPE_SEND_KEY</info><info>RADIUS_MICROSOFT_MS_MPPE_RECV_KEY</info><info>RADIUS_MICROSOFT_MS_RAS_VERSION</info><info>RADIUS_MICROSOFT_MS_OLD_ARAP_PASSWORD</info><info>RADIUS_MICROSOFT_MS_NEW_ARAP_PASSWORD</info><info>RADIUS_MICROSOFT_MS_ARAP_PASSWORD_CHANGE_REASON</info><info>RADIUS_MICROSOFT_MS_FILTER</info><info>RADIUS_MICROSOFT_MS_ACCT_AUTH_TYPE</info><info>RADIUS_MICROSOFT_MS_ACCT_EAP_TYPE</info><info>RADIUS_MICROSOFT_MS_CHAP2_RESPONSE</info><info>RADIUS_MICROSOFT_MS_CHAP2_SUCCESS</info><info>RADIUS_MICROSOFT_MS_CHAP2_PW</info><info>RADIUS_MICROSOFT_MS_PRIMARY_DNS_SERVER</info><info>RADIUS_MICROSOFT_MS_SECONDARY_DNS_SERVER</info><info>RADIUS_MICROSOFT_MS_PRIMARY_NBNS_SERVER</info><info>RADIUS_MICROSOFT_MS_SECONDARY_NBNS_SERVER</info><info>RADIUS_MICROSOFT_MS_ARAP_CHALLENGE</info>


id: RADIUS_VENDOR_SPECIFIC
type: constant
doc:
<comment>Description:</comment>
  The Vendor-Specific attribute. In general, vendor attribute values should be set using
  <strong>radius_put_vendor_addr()</strong>, <strong>radius_put_vendor_attr()</strong>, <strong>radius_put_vendor_int()</strong> and
  <strong>radius_put_vendor_string()</strong>, rather than directly.
  
  This constant is mostly useful when interpreting vendor specific attributes in responses from a
  RADIUS server; when a vendor specific attribute is received, the <strong>radius_get_vendor_attr()</strong> function
  should be used to access the vendor ID, attribute type and attribute value.


id: READLINE_LIB
type: constant
doc:
<comment>Description:</comment>
  The library which is used for readline support; currently either <return>readline</return> or <return>libedit</return>.


id: RNP_ENCRYPT_NOWRAP
type: constant
doc:
<comment>Description:</comment>
  Allows encryption of signed message. Message is not wrapped into literal data packet.


id: RNP_KEYSTORE_KBX
type: constant
doc:
<comment>Description:</comment>
  Keystore format "KBX". For public keys only. A keybox is a file format used to store public keys
  along with meta information and indices.


id: RNP_KEY_EXPORT_SUBKEYS
type: constant
doc:
<comment>Description:</comment>
  If primary key is being exported, all subkeys will be exported too.


id: RNP_KEY_REMOVE_SUBKEYS
type: constant
doc:
<comment>Description:</comment>
  If primary key is being deleted, all of its subkeys will be removed too.


id: RNP_LOAD_SAVE_PERMISSIVE
type: constant
doc:
<comment>Description:</comment>
  Allows to ignore bad signature/key/subkey packets during key import.


id: RNP_LOAD_SAVE_PUBLIC_KEYS
type: constant
doc:
<comment>Description:</comment>
  Load or save public keys only. Can be OR-ed with <info>RNP_LOAD_SAVE_SECRET_KEYS</info> to load both public and
  private keys to the FFI context or save them from the context.


id: RNP_LOAD_SAVE_SECRET_KEYS
type: constant
doc:
<comment>Description:</comment>
  Load or save secret keys only. Can be OR-ed with <info>RNP_LOAD_SAVE_PUBLIC_KEYS</info> to load both public and
  private keys to the FFI context or save them from the context.


id: RPMMIRE_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Search pattern is a regular expression with \., .* and ^...$ added.


id: RPMTAG_ENHANCENAME
type: constant
doc:
<comment>Description:</comment>
  Weak dependencies, with database index, requires librpm &gt;= 4.13.


id: RPMTAG_FILETRIGGERNAME
type: constant
doc:
<comment>Description:</comment>
  File trigger name, with database index, requires librpm &gt;= 4.13.


id: RPMTAG_RECOMMENDNAME
type: constant
doc:
<comment>Description:</comment>
  Recommended weak dependencies, with database index, requires librpm &gt;= 4.13.


id: RPMTAG_SUGGESTNAME
type: constant
doc:
<comment>Description:</comment>
  Suggested weak dependencies, with database index, requires librpm &gt;= 4.13.


id: RPMTAG_TRANSFILETRIGGERNAME
type: constant
doc:
<comment>Description:</comment>
  Transaction file trigger name, with database index, requires librpm &gt;= 4.13.


id: RRDCreator::__construct
type: function
doc:
<comment>Description:</comment>
  Creates new RRDCreator instance
  
  Creates new <class>RRDCreator</class> instance.

<comment>Param:</comment>
  <info>string</info>  <strong>$path</strong>       Path for newly created RRD database file.
  <info>string</info>  <strong>$startTime</strong>  Time for the first value in RRD database. Parameter supports all formats which
                      are supported by rrd create call.
  <info>int</info>     <strong>$step</strong>       Base interval in seconds with which data will be fed into the RRD database.


id: RRDCreator::addArchive
type: function
doc:
<comment>Description:</comment>
  Adds RRA - archive of data values for each data source
  
  Adds RRA definition by description of archive. Archive consists  of a number of data values or
  statistics for each of the defined data-sources (DS). Data sources are defined by method
  RRDCreator::addDataSource. You need call this method for each requested archive.

<comment>Param:</comment>
  <info>string</info>  <strong>$description</strong>  Definition of archive - RRA. This has same format as RRA definition in rrd
                        create command. See man page of rrd create for more details.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: RRDCreator::addDataSource
type: function
doc:
<comment>Description:</comment>
  Adds data source definition for RRD database
  
  RRD can accept input from several data sources (DS), e.g incoming and outgoing traffic. This
  method adds data source by description. You need call this method for each data source.

<comment>Param:</comment>
  <info>string</info>  <strong>$description</strong>  Definition of data source - DS. This has same format as DS definition in rrd
                        create command. See man page of rrd create for more details.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: RRDCreator::save
type: function
doc:
<comment>Description:</comment>
  Saves the RRD database to a file
  
  Saves the RRD database into file, which name is defined by RRDCreator::__construct.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: RRDGraph::__construct
type: function
doc:
<comment>Description:</comment>
  Creates new RRDGraph instance
  
  Creates new <class>RRDGraph</class> instance. This instance is responsible for rendering the result of RRD
  database query into image.

<comment>Param:</comment>
  <info>string</info>  <strong>$path</strong>  Full path for the newly created image.


id: RRDGraph::save
type: function
doc:
<comment>Description:</comment>
  Saves the result of query into image
  
  Saves the result of RRD database query into image defined by RRDGraph::__construct.

<comment>Return:</comment>
  <info>array</info>  Returns array with information about generated image, başarısızlık durumunda <info>false</info> döner.


id: RRDGraph::saveVerbose
type: function
doc:
<comment>Description:</comment>
  Saves the RRD database query into image and returns the verbose
     information about generated graph
    
  
  Saves the RRD database query into image file defined by method RRDGraph::__construct and returns
  the verbose information about generated graph, if "-" is used as image filename, image data are
  also returned in result array.

<comment>Return:</comment>
  <info>array</info>  Returns array with detailed information about generated image, başarısızlık durumunda <info>false</info>
         döner.


id: RRDGraph::setOptions
type: function
doc:
<comment>Description:</comment>
  Sets the options for rrd graph export

<comment>Param:</comment>
  <info>array</info>  <strong>$options</strong>  List of options for the image generation from the RRD database file. It can be
                   list of strings or list of strings with keys for better readability. Read the rrd
                   graph man pages for list of available options.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: RRDUpdater::__construct
type: function
doc:
<comment>Description:</comment>
  Creates new RRDUpdater instance
  
  Creates new RRDUpdater instance. This instance is responsible for updating the RRD database file.

<comment>Param:</comment>
  <info>string</info>  <strong>$path</strong>  Filesystem path for RRD database file, which will be updated.


id: RRDUpdater::update
type: function
doc:
<comment>Description:</comment>
  Update the RRD database file
  
  Updates the RRD file defined via RRDUpdater::__construct. The file is updated with a specific
  values.

<comment>Param:</comment>
  <info>array</info>   <strong>$values</strong>  Data for update. Key is data source name.
  <info>string</info>  <strong>$time</strong>    Time value for updating the RRD with a particular data. Default value is current
                   time.

<comment>Return:</comment>
  <info>bool</info>  Başarı durumunda <info>true</info>, başarısızlık durumunda <info>false</info> döner.


id: RUNKIT7_ACC_PRIVATE
type: constant
doc:
<comment>Description:</comment>
  Flag for <strong>runkit7_method_add()</strong> and <strong>runkit7_method_redefine()</strong> to make the method private.


id: RUNKIT7_ACC_PROTECTED
type: constant
doc:
<comment>Description:</comment>
  Flag for <strong>runkit7_method_add()</strong> and <strong>runkit7_method_redefine()</strong> to make the method protected.


id: RUNKIT7_ACC_PUBLIC
type: constant
doc:
<comment>Description:</comment>
  Flag for <strong>runkit7_method_add()</strong> and <strong>runkit7_method_redefine()</strong> to make the method public.


id: RUNKIT7_ACC_RETURN_REFERENCE
type: constant
doc:
<comment>Description:</comment>
  Include this flag to make the function or method being created or redeclared return a reference.


id: RUNKIT7_ACC_STATIC
type: constant
doc:
<comment>Description:</comment>
  Flag for <strong>runkit7_method_add()</strong> and <strong>runkit7_method_redefine()</strong> to make the method static.


id: RUNKIT7_FEATURE_SANDBOX
type: constant
doc:
<comment>Description:</comment>
  Always 0, it's impractical to implement the sandbox feature in php 7.


id: RUNKIT7_IMPORT_CLASSES
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag representing a bitwise OR of the <info>RUNKIT7_IMPORT_CLASS_*</info> constants.


id: RUNKIT7_IMPORT_CLASS_CONSTS
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that class constants should be imported from the specified file.


id: RUNKIT7_IMPORT_CLASS_METHODS
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that class methods should be imported from the specified file.


id: RUNKIT7_IMPORT_CLASS_PROPS
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that class standard properties should be imported from the
  specified file.


id: RUNKIT7_IMPORT_CLASS_STATIC_PROPS
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that class static properties should be imported from the
  specified file. Available since Runkit 1.0.1.


id: RUNKIT7_IMPORT_FUNCTIONS
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that normal functions should be imported from the specified file.


id: RUNKIT7_IMPORT_OVERRIDE
type: constant
doc:
<comment>Description:</comment>
  <strong>runkit7_import()</strong> flag indicating that if any of the imported functions, methods, constants, or
  properties already exist, they should be replaced with the new definitions.  If this flag is not
  set, then any imported definitions which already exist will be discarded.


id: Random\CryptoSafeEngine
type: class
doc:
<comment>Description:</comment>
  A marker interface indicating that the <info>Random\Engine</info> returns cryptographically secure randomness.


id: Random\Engine
type: class
doc:
<comment>Description:</comment>
  A <class>Random\Engine</class> provides a low-level source of randomness by returning random bytes that are
  consumed by high-level APIs to perform their operations. The <class>Random\Engine</class> interface allows
  swapping out the algorithm used to generate randomness, because each algorithm makes different
  tradeoffs to fit specific use-cases. Some algorithms are very fast, but generate lower-quality
  randomness, whereas other algorithms are slower, but generate better randomness, up to
  cryptographically secure randomness as provided by the <class>Random\Engine\Secure</class> engine.
  
  PHP provides several <class>Random\Engine</class>s out of the box to accomodate different use-cases. The
  <class>Random\Engine\Secure</class> engine that is backed by a CSPRNG is the recommended safe default choice,
  unless the application requires either reproducible sequences or very high performance.


id: Random\Engine::generate
type: function
doc:
<comment>Description:</comment>
  Generates randomness
  
  Returns randomness and advances the algorithm’s state by one step.
  
  The randomness is represented by a binary string containing random bytes. This representation
  allows to unambiguously interpret the random bits generated by the algorithm, for example to
  accomodate different output sizes used by different algorithms.
  
  Algorithms that natively operate on integer values should return the integer in little-endian byte
  order, for example by leveraging the <strong>pack()</strong> function with the <return>P</return> format code. The high-level
  interface provided by the <class>Random\Randomizer</class> will interpret the returned random bytes as unsigned
  little-endian integers if a numeric representation is required.
  
  It is strongly recommended that each bit of the returned string is uniformly and independently
  selected, as some applications require randomness based on the bit-level to work correctly. For
  example linear congruential generators often generate lower-quality randomness for the less
  significant bits of the return integer value and thus would not be appropriate for applications
  that require bit-level randomness.

<comment>Return:</comment>
  <info>string</info>  A non-empty string containing random bytes.
          
          The <class>Random\Randomizer</class> works with unsigned 64 bit integers internally. If the returned
          string contains more than 64 bit (8 byte) of randomness the exceeding bytes will be
          ignored. Other applications may be able to process more than 64 bit at once.


id: Random\Engine\Mt19937::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new Mt19937 engine
  
  Because the Mt19937 (“Mersenne Twister”) engine accepts only a single 32 bit integer as the seed,
  the number of possible random sequences is limited to just 232 (i.e. 4,294,967,296), despite
  Mt19937’s huge period of 219937-1.
  
  When relying on either implicit or explicit random seeding, duplications will appear much earlier.
  Duplicated seeds are expected with 50% probability after less than 80,000 randomly generated seeds
  according to the birthday problem. A 10% probability of a duplicated seed happens after randomly
  generating roughly 30,000 seeds.
  
  This makes Mt19937 unsuitable for applications where duplicated sequences must not happen with
  more than a negligible probability. If reproducible seeding is required, both the
  <class>Random\Engine\Xoshiro256StarStar</class> and <class>Random\Engine\PcgOneseq128XslRr64</class> engines support much larger
  seeds that are unlikely to collide randomly. If reproducibility is not required, the
  <class>Random\Engine\Secure</class> engine provides cryptographically secure randomness.
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>int|null</info>  <strong>$seed</strong>  Fills the state with values generated with a linear congruential generator that
                   was seeded with <strong>$seed</strong> interpreted as an unsigned 32 bit integer.
                   
                   If <strong>$seed</strong> is omitted or <info>null</info>, a random unsigned 32 bit integer will be used.
  <info>int</info>       <strong>$mode</strong>  Use one of the following constants to specify the implementation of the algorithm
                   to use. <info>MT_RAND_MT19937</info>: The correct Mt19937 implementation. <info>MT_RAND_PHP</info>: An
                   incorrect implementation for backwards compatibility with <strong>mt_srand()</strong> prior to PHP
                   7.1.0.
                   
                   Bu özelliğin kullanımı PHP 8.3.0
                   itibariyle ÖNERİLMEMEKTEDİR.
                   Bu özelliğe kesinlikle güvenilmemelidir.


id: Random\Engine\Mt19937::__debugInfo
type: function
doc:
<comment>Description:</comment>
  Returns the internal state of the engine
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>array</info>  


id: Random\Engine\Mt19937::__serialize
type: function
doc:
<comment>Description:</comment>
  Serializes the Mt19937 object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>array</info>  


id: Random\Engine\Mt19937::__unserialize
type: function
doc:
<comment>Description:</comment>
  Deserializes the data parameter into a Mt19937 object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>array</info>  <strong>$data</strong>  

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Random\Engine\Mt19937::generate
type: function
doc:
<comment>Description:</comment>
  Generate 32 bits of randomness
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>string</info>  A string representing an unsigned 32 bit integer in little-endian order.


id: Random\Engine\PcgOneseq128XslRr64
type: class
doc:
<comment>Description:</comment>
  Implements a Permuted congruential generator (PCG) with 128 bits of state, XSL and RR output
  transformations, and 64 bits of output.


id: Random\Engine\PcgOneseq128XslRr64::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new PCG Oneseq 128 XSL RR 64 engine
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string|int|null</info>  <strong>$seed</strong>  How the internal 128 bit (16 byte) state consisting of one unsigned 128
                          bit integer is seeded depends on the type used as the <strong>$seed</strong>.
                          TypeAçıklama<info>null</info> Fills the state with 16 random bytes generated using the
                          CSPRNG. <info>int</info> Fills the state by setting the state to <return>0</return>, advancing the
                          engine one step, adding the value of <strong>$seed</strong> interpreted as an unsigned 64
                          bit integer, and advancing the engine another step. <info>string</info> Fills the state
                          by interpreting a 16 byte <info>string</info> as a little-endian unsigned 128 bit
                          integer.


id: Random\Engine\PcgOneseq128XslRr64::__serialize
type: function
doc:
<comment>Description:</comment>
  Serializes the PcgOneseq128XslRr64 object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>array</info>  


id: Random\Engine\PcgOneseq128XslRr64::__unserialize
type: function
doc:
<comment>Description:</comment>
  Deserializes the data parameter into a PcgOneseq128XslRr64 object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>array</info>  <strong>$data</strong>  

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Random\Engine\PcgOneseq128XslRr64::generate
type: function
doc:
<comment>Description:</comment>
  Generate 64 bits of randomness
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>string</info>  A string representing an unsigned 64 bit integer in little-endian order.


id: Random\Engine\PcgOneseq128XslRr64::jump
type: function
doc:
<comment>Description:</comment>
  Efficiently move the engine ahead multiple steps
  
  Moves the algorithm’s state ahead by the number of steps given by <strong>$advance</strong>, as if
  <strong>Random\Engine\PcgOneseq128XslRr64::generate()</strong> was called that many times.

<comment>Param:</comment>
  <info>int</info>  <strong>$advance</strong>  The number of steps to move ahead; must be <return>0</return> or greater.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Random\Engine\Secure
type: class
doc:
<comment>Description:</comment>
  Generates cryptographically secure randomness using the operating system’s CSPRNG.
  
  The randomness generated by this <class>Random\Engine</class> is suitable for all applications, including the
  generation of long-term secrets, such as encryption keys.
  
  The <class>Random\Engine\Secure</class> engine is the recommended safe default choice, unless the application
  requires either reproducible sequences or very high performance.


id: Random\Engine\Secure::generate
type: function
doc:
<comment>Description:</comment>
  Generate cryptographically secure randomness
  
  Returns cryptographically secure randomness.
  
  Öncelik sırasına göre rastgelelik kaynakları aşağıdaki gibidir:
  
  Linux: getrandom(), /dev/urandom.
  
  FreeBSD &gt;= 12 (PHP &gt;= 7.3): getrandom(), /dev/urandom
  
  Windows (PHP &gt;= 7.2): CNG-API
  
  Windows: CryptGenRandom
  
  macOS (PHP &gt;= 8.2; &gt;= 8.1.9; &gt;= 8.0.22 if CCRandomGenerateBytes is available at compile
  time): CCRandomGenerateBytes()
  
  macOS (PHP &gt;= 8.1; &gt;= 8.0.2): arc4random_buf(), /dev/urandom
  
  NetBSD &gt;= 7 (PHP &gt;= 7.1; &gt;= 7.0.1): arc4random_buf(), /dev/urandom
  
  OpenBSD &gt;= 5.5 (PHP &gt;= 7.1; &gt;= 7.0.1): arc4random_buf(), /dev/urandom
  
  DragonflyBSD (PHP &gt;= 8.1): getrandom(), /dev/urandom
  
  Solaris (PHP &gt;= 8.1): getrandom(), /dev/urandom
  
  Daha önce belirtilmeyen herhangi bir işletim sistemi ve PHP sürümü birleşimi: /dev/urandom
  
  Kaynaklardan hiçbiri kullanılabilir değilse veya hiçbiri rasgelelik üretemezse, bir
  <class>Random\RandomException</class> oluşur.

<comment>Return:</comment>
  <info>string</info>  A string containing <info>PHP_INT_SIZE</info> cryptographically secure random bytes.


id: Random\Engine\Xoshiro256StarStar::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new xoshiro256** engine
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>string|int|null</info>  <strong>$seed</strong>  How the internal 256 bit (32 byte) state consisting of four unsigned 64
                          bit integers is seeded depends on the type used as the <strong>$seed</strong>.
                          TypeAçıklama<info>null</info> Fills the state with 32 random bytes generated using the
                          CSPRNG. <info>int</info> Fills the state with four consecutive values generated with
                          the SplitMix64 algorithm that was seeded with <strong>$seed</strong> interpreted as an
                          unsigned 64 bit integer. <info>string</info> Fills the state by interpreting a 32 byte
                          <info>string</info> as four little-endian unsigned 64 bit integers.


id: Random\Engine\Xoshiro256StarStar::__serialize
type: function
doc:
<comment>Description:</comment>
  Serializes the Xoshiro256StarStar object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>array</info>  


id: Random\Engine\Xoshiro256StarStar::__unserialize
type: function
doc:
<comment>Description:</comment>
  Deserializes the data parameter into a Xoshiro256StarStar object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>array</info>  <strong>$data</strong>  

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Random\Engine\Xoshiro256StarStar::jump
type: function
doc:
<comment>Description:</comment>
  Efficiently move the engine ahead by 2^128 steps
  
  Moves the algorithm’s state ahead by 2128 steps, as if
  <strong>Random\Engine\Xoshiro256StarStar::generate()</strong> was called 2128 times.
  
  The purpose of a jump is to facilitate the creation of a new <class>Random\Engine\Xoshiro256StarStar</class>
  engine from an existing seeded <class>Random\Engine\Xoshiro256StarStar</class> engine. The seeded engine acts as
  a blueprint, which can be cloned and repeatedly jumped to create 2128 non-overlapping sequences
  with 2128 values each.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Random\Engine\Xoshiro256StarStar::jumpLong()</strong>


id: Random\Engine\Xoshiro256StarStar::jumpLong
type: function
doc:
<comment>Description:</comment>
  Efficiently move the engine ahead by 2^192 steps
  
  Moves the algorithm’s state ahead by 2192 steps, as if
  <strong>Random\Engine\Xoshiro256StarStar::generate()</strong> was called 2192 times.
  
  The purpose of a long jump is to facilitate the creation of a new <class>Random\Engine\Xoshiro256StarStar</class>
  engine from an existing seeded <class>Random\Engine\Xoshiro256StarStar</class> engine. The seeded engine acts as
  a blueprint, which can be cloned and repeatedly jumped to create 264 non-overlapping sequences
  with 2192 values each.
  
  Long jumping may be combined with <strong>Random\Engine\Xoshiro256StarStar::jump()</strong>ing to further split
  each of the 264 sequences generated by long jumping, into 264 sequences of 2128 values each.

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.

<comment>See Also:</comment>
   * <strong>Random\Engine\Xoshiro256StarStar::jump()</strong>


id: Random\RandomError
type: class
doc:
<comment>Description:</comment>
  Indicates that the used <class>Random\Engine</class> is broken, e.g. because it is severely biased.


id: Random\Randomizer
type: class
doc:
<comment>Description:</comment>
  Provides a high-level API to the randomness provided by an <class>Random\Engine</class>.


id: Random\Randomizer::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new Randomizer
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>Random\Engine|null</info>  <strong>$engine</strong>  The <class>Random\Engine</class> to use to generate randomness.
                               
                               If <strong>$engine</strong> is omitted or <info>null</info>, a new <class>Random\Engine\Secure</class> object will
                               be used.


id: Random\Randomizer::__serialize
type: function
doc:
<comment>Description:</comment>
  Serializes the Randomizer object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>array</info>  


id: Random\Randomizer::__unserialize
type: function
doc:
<comment>Description:</comment>
  Deserializes the data parameter into a Randomizer object
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>array</info>  <strong>$data</strong>  

<comment>Return:</comment>
  <info>void</info>  Hiçbir değer dönmez.


id: Random\Randomizer::getBytes
type: function
doc:
<comment>Description:</comment>
  Get random bytes
  
  Generates a string containing uniformly selected random bytes with the requested <strong>$length</strong>.
  
  As the returned bytes are selected completely randomly, the resulting string is likely to contain
  unprintable characters or invalid UTF-8 sequences. It may be necessary to encode it before
  transmission or display.

<comment>Param:</comment>
  <info>int</info>  <strong>$length</strong>  The length of the random <info>string</info> that should be returned in bytes; must be <return>1</return> or
                greater.

<comment>Return:</comment>
  <info>string</info>  A <info>string</info> containing the requested number of random bytes.

<comment>See Also:</comment>
   * <strong>random_bytes()</strong>
   * <strong>bin2hex()</strong>
   * <strong>base64_encode()</strong>
   * Random\Randomizer::getBytesFromString


id: Random\Randomizer::getBytesFromString
type: function
doc:
<comment>Description:</comment>
  Get random bytes from a source string
  
  Generates a string containing uniformly selected random bytes from the input <strong>$string</strong> with the
  requested <strong>$length</strong>.
  
  The chance for a byte to be selected is proportional to its share of the input <strong>$string</strong>. If each
  byte occurs the same amount of times, each byte is equally likely to be selected.

<comment>Param:</comment>
  <info>string</info>  <strong>$string</strong>  The <info>string</info> from which the returned bytes are selected.
  <info>int</info>     <strong>$length</strong>  The length of the random <info>string</info> that should be returned in bytes; must be <return>1</return> or
                   greater.

<comment>Return:</comment>
  <info>string</info>  A <info>string</info> containing the requested number of random bytes taken from the input <strong>$string</strong>.

<comment>See Also:</comment>
   * Random\Randomizer::getBytes


id: Random\Randomizer::getFloat
type: function
doc:
<comment>Description:</comment>
  Get a uniformly selected float
  
  Returns a uniformly selected, equidistributed float from a requested interval.
  
  Due to the limited precision, not all real numbers can be exactly represented as a floating point
  number.
   If a number cannot be represented exactly, it is rounded to the nearest representable exact
  value.
   Furthermore, floats are not equally dense across the whole number line.
   Because floats use a binary exponent, the distance between two neighboring floats doubles at each
  power of two.
   In other words: There are the same number of representable floats between <return>1.0</return> and <return>2.0</return> as they are
  between <return>2.0</return> and <return>4.0</return>, <return>4.0</return> and <return>8.0</return>, <return>8.0</return> and <return>16.0</return>, and so on.
  
  Randomly sampling an arbitrary number within the requested interval, for example by dividing two
  integers, might result in a biased distribution for this reason.
   The necessary rounding will cause some floats to be returned more often than others, especially
  around powers of two when the density of floats changes.
  
  Random\Randomizer::getFloat implements an algorithm that will return a uniformly selected float
  from the largest possible set of exactly representable and equidistributed floats within the
  requested interval.
   The distance between the selectable floats (“step size”) matches the distance between the floats
  with the lowest density, i.e. the distance between floats at interval boundary with the larger
  absolute value.
   This means that not all representable floats within a given interval may be returned if the
  interval crosses one or more powers of two.
   Stepping will start from the interval boundary with the larger absolute value to ensure the steps
  align with the exactly representable floats.
  
  Closed interval boundaries will always be included in the set of selectable floats.
   Thus, if the size of the interval is not an exact multiple of the step size and the boundary with
  the smaller absolute value is a closed boundary, the distance between that boundary and its
  nearest selectable float will be smaller than the step size.
  
  Post-processing the returned floats is likely going to break the uniform equidistribution, because
  the intermediate floats within a mathematical operation are experiencing implicit rounding.
   The requested interval should match the desired interval as closely as possible and rounding
  should only be performed as an explicit operation right before displaying the selected number to a
  user.
  
  To give an example of how the algorithm works, consider a floating point representation that uses
  a 3-bit mantissa.
   This representation is capable of representing 8 different floating point values between
  consecutive powers of two.
   This means that between <return>1.0</return> and <return>2.0</return> all steps of size <return>0.125</return> are exactly representable and between
  <return>2.0</return> and <return>4.0</return> all steps of size <return>0.25</return> are exactly representable.
   In reality PHP’s floats use a 52-bit mantissa and can represent 252 different values between each
  power of two.
   This means that <return>1.0</return><return>1.125</return><return>1.25</return><return>1.375</return><return>1.5</return><return>1.625</return><return>1.75</return><return>1.875</return><return>2.0</return><return>2.25</return><return>2.5</return><return>2.75</return><return>3.0</return><return>3.25</return><return>3.5</return><return>3.75</return><return>4.0</return> are the exactly
  representable floats between <return>1.0</return> and <return>4.0</return>.
  
  Now consider that $randomizer-&gt;getFloat(1.625, 2.5, IntervalBoundary::ClosedOpen) is called,
  i.e. a random float starting at <return>1.625</return> until, but not including, <return>2.5</return> is requested.
   The algorithm first determines the step size at the boundary with the larger absolute value
  (<return>2.5</return>). The step size at that boundary is <return>0.25</return>.
  
  Note that the size of the requested interval is <return>0.875</return>, which is not an exact multiple of <return>0.25</return>.
   If the algorithm would start stepping at the lower bound <return>1.625</return>, it would encounter <return>2.125</return>, which
  is not exactly representable and would experience implicit rounding.
   Thus the algorithm starts stepping at the upper boundary <return>2.5</return>.
   The selectable values are: <return>2.25</return><return>2.0</return><return>1.75</return><return>1.625</return>
   <return>2.5</return> is not included, because the upper boundary of the requested interval is an open boundary.
   <return>1.625</return> is included, even though its distance to the nearest value <return>1.75</return> is <return>0.125</return>, which is smaller
  than the previously determined step size of <return>0.25</return>.
   The reason for that is that the requested interval is closed at the lower boundary (<return>1.625</return>) and
  closed boundaries are always included.
  
  Finally the algorithm uniformly selects one of the four selectable values at random and returns
  it.
  
  In the previous example, there are eight representable floating point numbers between each
  sub-interval delimited by a power of two.
   To give an example why dividing two integers would not work well to generate a random float,
  consider that there are 16 equidistributed floating point numbers in the right-open interval from
  <return>0.0</return> until, but not including, <return>1.0</return>. Half of them are the eight exactly representable values between
  <return>0.5</return> and <return>1.0</return>, the other half are the values between <return>0.0</return> and <return>1.0</return> that the step size of <return>0.0625</return>.
   These can easily be generated by dividing a random integer between <return>0</return> and <return>15</return> by <return>16</return> to obtain one
  of:
   <return>0.0</return><return>0.0625</return><return>0.125</return><return>0.1875</return><return>0.25</return><return>0.3125</return><return>0.375</return><return>0.4375</return><return>0.5</return><return>0.5625</return><return>0.625</return><return>0.6875</return><return>0.75</return><return>0.8125</return><return>0.875</return><return>0.9375</return>
  
  This random float could be scaled to right-open interval from <return>1.625</return> until, but not including, <return>2.75</return>
  by multiplying it with the size of the interval (<return>0.875</return>) and adding the minimum <return>1.625</return>. This
  so-called affine transformation would result in the values:
   <return>1.625</return> rounded to <return>1.625</return><return>1.679</return> rounded to <return>1.625</return><return>1.734</return> rounded to <return>1.75</return><return>1.789</return> rounded to <return>1.75</return><return>1.843</return>
  rounded to <return>1.875</return><return>1.898</return> rounded to <return>1.875</return><return>1.953</return> rounded to <return>2.0</return><return>2.007</return> rounded to <return>2.0</return><return>2.062</return> rounded to
  <return>2.0</return><return>2.117</return> rounded to <return>2.0</return><return>2.171</return> rounded to <return>2.25</return><return>2.226</return> rounded to <return>2.25</return><return>2.281</return> rounded to <return>2.25</return><return>2.335</return>
  rounded to <return>2.25</return><return>2.390</return> rounded to <return>2.5</return><return>2.445</return> rounded to <return>2.5</return>
   Note how the upper boundary of <return>2.5</return> would be returned, despite being an open boundary and thus
  being excluded.
   Also note how <return>2.0</return> and <return>2.25</return> are twice as likely to be returned compared to the other values.

<comment>Param:</comment>
  <info>float</info>                    <strong>$min</strong>       The lower bound of the interval.
  <info>float</info>                    <strong>$max</strong>       The upper bound of the interval.
  <info>Random\IntervalBoundary</info>  <strong>$boundary</strong>  Specifies whether the interval boundaries are possible return
                                      values.

<comment>Return:</comment>
  <info>float</info>  A uniformly selected, equidistributed float from the interval specified by <strong>$min</strong>, <strong>$max</strong>, and
         <strong>$boundary</strong>.
          Whether <strong>$min</strong> and <strong>$max</strong> are possible return values depends on the value of <strong>$boundary</strong>.

<comment>See Also:</comment>
   * Random\Randomizer::nextFloat
   * Random\Randomizer::getInt


id: Random\Randomizer::getInt
type: function
doc:
<comment>Description:</comment>
  Get a uniformly selected integer
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Param:</comment>
  <info>int</info>  <strong>$min</strong>  The lowest value to be returned.
  <info>int</info>  <strong>$max</strong>  The highest value to be returned.

<comment>Return:</comment>
  <info>int</info>  A uniformly selected integer from the closed interval [<strong>$min</strong>, <strong>$max</strong>]. Both <strong>$min</strong> and <strong>$max</strong> are
       possible return values.

<comment>See Also:</comment>
   * <strong>random_int()</strong>
   * Random\Randomizer::getFloat


id: Random\Randomizer::nextFloat
type: function
doc:
<comment>Description:</comment>
  Get a float from the right-open interval [0.0, 1.0)
  
  Returns a uniformly selected, equidistributed float from the right-open interval from <return>0.0</return> until,
  but not including, <return>1.0</return>.
  
  The chance for returned float to be within a given right-open sub-interval is proportial to the
  size of the sub-interval.
   This means that the chance for a float to be less than <return>0.5</return> is 50 %, which is equal to the chance
  for a float to be at least <return>0.5</return>.
   Likewise the chance for a float to be within the right-open interval from <return>0.2</return> until, but not
  including, <return>0.25</return> is exactly 5 %.
  
  This property makes it easy to leverage Random\Randomizer::nextFloat to generate a random boolean
  with a given chance by checking if the returned float is less than a given chance.
  
  The domain of the returnable floats of Random\Randomizer::nextFloat is identical to that of
  Randomizer::getFloat(0.0, 1.0, IntervalBoundary::ClosedOpen).
  
  The internal implementation of Random\Randomizer::nextFloat is more efficient.
  
  Scaling the return value to a different interval using multiplication or addition (a so-called
  affine transformation) might result in a bias in the resulting value as floats are not equally
  dense across the number line. As not all values can be exactly represented by a float, the result
  of the affine transformation might also result in values outside of the requested interval due to
  implicit rounding.
   An in-depth explanation of the problems with the affine transformation is given in the
  documentation for Random\Randomizer::getFloat.
  
  Use Random\Randomizer::getFloat to generate a random float within an arbitrary interval. Use
  Random\Randomizer::getInt to generate a random integer within an arbitrary interval.

<comment>Return:</comment>
  <info>float</info>  A uniformly selected, equidistributed float from the right-open
         (<return>IntervalBoundary::ClosedOpen</return>) interval [0.0, 1.0).
          <return>0.0</return> is a possible return value, <return>1.0</return> is not.

<comment>See Also:</comment>
   * Random\Randomizer::getFloat


id: Random\Randomizer::nextInt
type: function
doc:
<comment>Description:</comment>
  Get a positive integer
  
  Bu işlev hala
  belgelendirilmemiştir; sadece bağımsız değişken listesi
  mevcuttur.

<comment>Return:</comment>
  <info>int</info>  A positive integer between 0 and a maximum value depending on the number of bytes returned
       from Random\Engine::generate. The exact maximum can be calculated as 2$engine_bytes * 8 - 1 -
       1.


