File Manager

X7ROOT File Manager

Current Path: /opt/cpanel/ea-php72/root/usr/share/doc/ea-php72-php-common

opt / cpanel / ea-php72 / root / usr / share / doc / ea-php72-php-common /

ðŸ“ ..
ðŸ“„ CODING_STANDARDS(11.68 KB)
ðŸ“„ CREDITS(91 B)
ðŸ“„ EXTENSIONS(20.61 KB)
ðŸ“„ LICENSE(3.13 KB)
ðŸ“„ NEWS(117.26 KB)
ðŸ“„ README.EXT_SKEL(6.83 KB)
ðŸ“„ README.GIT-RULES(4.99 KB)
ðŸ“„ README.MAILINGLIST_RULES(3.35 KB)
ðŸ“„ README.NEW-OUTPUT-API(5.11 KB)
ðŸ“„ README.PARAMETER_PARSING_API(7.34 KB)
ðŸ“„ README.REDIST.BINS(19.25 KB)
ðŸ“„ README.RELEASE_PROCESS(14.04 KB)
ðŸ“„ README.SELF-CONTAINED-EXTENSIONS(4.96 KB)
ðŸ“„ README.STREAMS(14.96 KB)
ðŸ“„ README.SUBMITTING_PATCH(7.93 KB)
ðŸ“„ README.TESTING(6.53 KB)
ðŸ“„ README.TESTING2(4.83 KB)
ðŸ“„ README.UNIX-BUILD-SYSTEM(4.16 KB)
ðŸ“„ README.WIN32-BUILD-SYSTEM(114 B)
ðŸ“„ README.input_filter(5.29 KB)
ðŸ“„ README.md(1.57 KB)
ðŸ“„ TSRM_LICENSE(1.28 KB)
ðŸ“„ ZEND_LICENSE(2.74 KB)
ðŸ“„ libmagic_LICENSE(1.63 KB)
ðŸ“„ phar_LICENSE(4.57 KB)
ðŸ“„ php.ini-development(69.56 KB)
ðŸ“„ php.ini-production(69.74 KB)

Editing: README.EXT_SKEL

(NOTE: you may also want to take a look at the pear package
	     PECL_Gen, a PHP-only alternative for this script that
			 supports way more extension writing tasks and is
			 supposed to replace ext_skel completely in the long run ...)

WHAT IT IS

It's a tool for automatically creating the basic framework for a PHP module
  and writing C code handling arguments passed to your functions from a simple
  configuration file. See an example at the end of this file.

HOW TO USE IT

Very simple. First, change to the ext/ directory of the PHP 4 sources. If
  you just need the basic framework and will be writing all the code in your
  functions yourself, you can now do

./ext_skel --extname=module_name

and everything you need is placed in directory module_name.

[ Note that GNU awk is likely required for this script to work.  Debian
    systems seem to default to using mawk, so you may need to change the
    #! line in skeleton/create_stubs and the cat $proto | awk line in
    ext_skel to use gawk explicitly. ]

If you don't need to test the existence of any external header files,
  libraries or functions in them, the module is already almost ready to be
  compiled in PHP.  Just remove 3 comments in your_module_name/config.m4,
  change back up to PHP sources top directory, and do

./buildconf; ./configure --enable-module_name; make

The definition of PHP_MODULE_NAME_VERSION will be present in the
  php_module_name.h and injected into the zend_module_entry definition. This
  is required by the PECL website for the version string conformity checks
  against package.xml

But if you already have planned the overall scheme of your module, what
  functions it will contain, their return types and the arguments they take
  (a very good idea) and don't want to bother yourself with creating function
  definitions and handling arguments passed yourself, it's time to create a
  function definitions file, which you will give as an argument to ext_skel
  with option

--proto=filename.

SOURCE AND HEADER FILE NAME

./ext_skel generates 'module_name.c' and 'php_module_name.h' as main source
  and header files. Keep these names.

Module functions (User functions) must be named

module_name_function()

When you need to expose module functions to other modules, expose functions
  strictly needed by others. Exposed internal function must be named

php_module_name_function()

X7ROOT File Manager

Editing: README.EXT_SKEL

Upload File

Create Folder