Download the PHP package phunkie/phunkiec without Composer
On this page you can find all versions of the php package phunkie/phunkiec. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download phunkie/phunkiec
More information about phunkie/phunkiec
Files in phunkie/phunkiec
Package phunkiec
Short Description Phunkie preprocessor CLI — compiles .phunkie files into standard PHP
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phunkiec
phunkiec
The Phunkie preprocessor. It compiles .phunkie files into standard PHP: for
comprehensions and pattern matching are desugared at compile time, so there is no
runtime cost.
Usage
<input>— a.phunkiefile or a directory of them.--out/-o— output file or directory (required).--watch/-w— keep running, recompiling a source as it is saved.--macro-dir/-m— an extra directory of.synmacros (repeatable).--macro-file/-f— an extra.synmacro file (repeatable).
A short option takes its value either way round, -o build or -o=build.
A .phunkie file is only ever PHP, so it need not say <?php. The compiler
opens the file for you, on its own first line. A source that opens its own tag
is left exactly as written, so nothing already written has to change.
Watching
Everything under src is compiled once, and then the directory is watched.
Saving a source recompiles that source alone, into the same place under build
that it holds under src, and reports it:
A new source is picked up without restarting. A source that fails to compile is reported and the watch carries on, so a half-written save costs nothing but the next save.
Changes are noticed by polling four times a second, comparing the contents of
each source rather than its timestamp: filemtime has one-second resolution, so
two saves inside the same second are indistinguishable by time and the second
would be missed.
Removing a source leaves the PHP it produced behind. Deleting generated files on the strength of a poll is a worse failure than leaving one to be cleaned up.
Macros
phunkiec loads macros from three places, highest precedence first (the first matching rule wins):
- Explicit — anything passed with
--macro-file/--macro-dir. - Discovered — macros shipped by installed composer packages (see below).
- Bundled — the rules that ship with phunkiec, in its own
macros/.
So a package's rule overrides a bundled one for the same surface syntax, and an explicitly supplied macro overrides everything.
Shipping macros from a package
A library can ship .syn macros for its own types and have phunkiec discover
them automatically. Declare a macros directory in the package's composer.json:
Every .syn file in that directory is loaded whenever phunkiec compiles a project
that has the package installed. This is how phunkie/effect ships the pattern for
its own IO — matching an effect IO needs a rule pointing at effect's
Referenced\IO, which phunkiec itself does not know about.
Discovery uses composer's runtime metadata (Composer\InstalledVersions), so it
sees exactly the packages installed alongside the project being compiled.
All versions of phunkiec with dependencies
md/syn Version ^0.2
symfony/console Version ^7.0
symfony/finder Version ^7.0