This fragment is about to be reported (you'll remain on this page): You can enter a comment to clarify the mistake if you would like to: |
Inspired by this post on Laravel forums.
In short, suppose you're writing a simple oldschool browser quest game where the user makes choices to advance in the story. Or perhaps you're making an online testing resource and want the user to be able to save his progrss without the need to register or keep track of his sessions – by simply bookmarking the current page.
Choices can be saved directly like this:
A personal RSS/Atom feed in every home.
Feeder is a syndication framework for PHP 5+. It generates RSS 0.92, RSS 2.0 and Atom feeds from single data source. Bundled Text Feeder generates feeds from text files so you don't have to do any coding at all to get your channel running. And, since it's part of Feeder, it outputs in all three supported feed formats.
All Feeder classes and related data is released under public domain. If you use it I'll appreciate a backlink to this page; if you have feedback – feel free to drop a comment.
Standalone PHP class for processing bencoding-encoded data, such as bit-torrent files.
BEncoded is a PHP OOP wrapper for two lightenc.php functions from Theory.org for manipulating bencoded data. It lets you transform bencoded files, retrieve data from them, add some, delete, calculate info hashes and do other things using a simple interface.
Can't want to see? Download now or view its source.
First version on 1 July 2011; last update on 23 January 2012.
My reference document based on official RSS/Atom specifications.
This is a reference document I have made for myself in preparation to writing a universal PHP feed creator class. I have studied both RSS 0.92 & 2.0 specs and RFC 4287 that stands for The Atom Syndication Format (Atom 1.0).
I'll give a brief intro into the RSS versions here because they might be confusing at first glance (asides from Atom which has them straightforward).
There are 2 branches of the RSS format: RDF-like (0.90, 1.0 and 1.1) and XML-valid (0.91, 0.92 and 2.0). The first retains more of the original Netscape specification, RSS standing for RDF Site Summary. The second is a simplified, improved and XML-compliant format that is most popular among the two and Atom (not less than 50% of all feeds according to Wikipedia.
gzencode() function exists since PHP 4 but gzdecode() - only since PHP 6.
Build-in PHP function gzencode compresses a string with all the necessary headings the GZIP specification describes (this is what differs it from gzcompress that omits those headers). However, there's no counterpart gzdecode function – at least if you can't rely on PHP 6 yet.
Lucky for us, there's a function called readgzfile that does the same thing as gzdecode except that it reads GZ data from a file and sends the decompressed string to stdout. We can use this function to imitate gzdecode:
The only difference between the above code and real gzdecode is that the latter returns false on error while the above returns null. The reason for this is because I'm always preferring null over false so I don't have to remember which functions return which «failure value» – look at standard PHP functions half of which return null and another – false (and some others – empty string or -1).
P.S.: you'd probably only need gzdecode in case you need reading or writing the data in standard GZIP format that's produced by a third party library such as those from ZLib.net. In case of server-side-only processing you can use gzcompress / gzdecompress that are both available since PHP 4.
Unified formatting for all electronic documents.
Roughly a year ago I've met (actually, re-met after 3 years) Freeman
who among other crazy ideas had the idea of a global text markup language used wordwide,
international and extensible.
Well, this idea isn't new and he certainly didn't invent all of it. Neither did I.But together we've formed something I'm personally proud of – the ObjectWacko markup language.
ObjectWacko is based on a markup language initially created for WakkaWiki which was later forked into WackoWiki which has been abandoned nearly 7 years ago and is now retaken by another team.
Core principles of a human-writable markup are:
PHP/(?<=\s)--(?=\s)/ → "—" and consider -- having both left and right spaces as em-dash, otherwise it's a formatted text block. But what to do with typographic dash "--" is...? Include " in the regexp? But if we use «*» to format bold text (em-dash "**--**" is used to...) – how to differentiate between strikethru token and the dash? Aww, so many questions… Let's say we need to display a code snippet on some web page. Program sources usually use highlighted syntax (but that's not the topic of this post) and also display line numbers. We can do the latter in several different ways and I'll outline them below – but in case you want an instant CSS solution you'll find it below here.
First off, we can simply enumerate lines using PHP like this:
A workaround to catch E_FATAL, E_PARSE and other core PHP errors.
PHP has a habit of terminating script with no chances to do anything when a «non-catchable error» occurs. Here non-catchable means pretty much any error: fatal errors, parse errors, regular errors and all those errors triggered by PHP core (constants beginning with E_CORE_ prefix such as E_CORE_ERROR).
However, there's a solution – well, not perfect but at least it allows us catch even fatal errors that PHP might raise: by means of a shutdown function. I found it in the comments to PHP's set_error_handler function, tested it and it actually worked – I was able to handle even compile errors.
Pretty simple. This way your script can continue execution even after a severe PHP error (like calling an undeclared function or class). However, there's one point:
Недавние комментарии
«Stage Once» – a Visual Novel hacking tutorial
Part 1 – the Bruteforce
Today's vectors
Encoding choices as a secure string
Рога и копыта