Bolinha1

<?php 
namespace Arquivo;
use Exception;
class TransformaCsvEmArray
{
	private $arquivo;
	private $cabecalho;

	public function __construct($arquivo, TransformaCabecalhoCsvEmArray $cabecalho)
	{

mathiasverraes

<?php
function it($m,$p){echo ($p?'✔︎':'✘')." It $m\n"; if(!$p){$GLOBALS['f']=1;}}function done(){if(@$GLOBALS['f'])die(1);}

Sodaware

(defun phing-call (target)
  "Call Phing's build.xml"
  
  ;; Ask for target to execute
  (interactive "MPhing Target: ")
  
  ;; Open a new *phing-compilation* buffer & kill the old one
  (let ((oldbuf (get-buffer "*phing-compilation*")))
    (if (not (null oldbuf))
        (kill-buffer "*phing-compilation*")))

Bolinha1

<?php

namespace Upload;
class Upload
{
	public  $definePath = '';
	private $path;
	
	public function __construct($definePath, $path = 'arquivos/')
	{

aaronpk

[[email protected] www]$ cat .htaccess 
RewriteEngine on
RewriteCond %{QUERY_STRING} resource=acct:(.+)
RewriteRule ^\.well-known/webfinger /profile/%1? [L]

[[email protected] www]$ cat profile/[email protected]
{
  "subject": "acct:[email protected]",
  "links": [
    {

Bolinha1

<?php
class DesvioPadrao 
{
   private $amostra;

   public function __construct($amostra)
   {
        $this->amostra = explode(',', $amostra);
   }
   

alganet

<?php

// Simple empty matching. Explains a lot of how the idea works:
//
// By default, expressions are delimited by a line, which 
// implies /^$/. Everything goes inside that. Calling nothing 
// else more matches any line.
//
// p() is a function call. Could be Pattern::create(), but I
// believe providing a function is sane. It can be provided

alganet

<?php

// Matches a single char. Equivalent to: /./

Pattern::char()->test('a');         //true
Pattern::char()->replace('a', 'b'); //b
Pattern::char()->match('a');        //array('a') (captures groups)

// Possible "steps":

nikic

Why objects (usually) use less memory than arrays in PHP

This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)

The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array part of it away. So how does that work?

The key here is that objects usually have a predefined set of keys, whereas arrays don't:

henriquemoody

# Bash-Completion script for PHPUnit
#
# Created by Henrique Moody <[email protected]>
#
_phpunit()
{
    COMPREPLY=()

    local cur="${COMP_WORDS[COMP_CWORD]}"
    local prev="${COMP_WORDS[COMP_CWORD-1]}"