Stubblog - Comments

Frank: vfsStream 0.10.0 released

nospam@example.com (Frank) — Fri, 22 Jul 2011 17:34:02 +0200

So auf Anhieb sehe ich nichts, evtl. zwei Dinge:
- Das Werfen einer Exception aus dem stream wrapper heraus versuche ich immer zu vermeiden.

- Das Verschieben des eigentlichen Ladens auf den Zeitpunkt des "echten" Zugriffs könnte ggf. ein Problem sein. Wie wird signalisiert, wenn es zu diesem Zeitpunkt ein Problem mit dem Zugriff gibt?

Lukas: vfsStream 0.10.0 released

nospam@example.com (Lukas) — Fri, 22 Jul 2011 16:42:40 +0200

Ahoi,

nen bissel am thema vorbei .. naja halb .. aber ihr seit ja userland php stream wrapper experten. ich habe das ganze noch nicht im detail studiert, aber ein kollege hat regelmaessige seg faults auf den stream wrapper in jackalope zurueck gefuehrt:
https://github.com/jackalope/jackalope/blob/master/src/Jackalope/BinaryStreamWrapper.php

vielleicht faellt euch da auf den ersten blick auf falls wir da was "dummes" tun.

Frank: vfsStream 0.9.0 released

nospam@example.com (Frank) — Fri, 22 Jul 2011 15:48:15 +0200

Thanks.

Zilvinas: vfsStream 0.9.0 released

nospam@example.com (Zilvinas) — Thu, 21 Jul 2011 10:56:23 +0200

Hi,

Just writing to say I appreciate the work you're doing. Thanks for a new release

aditya menon: Traits for PHP

nospam@example.com (aditya menon) — Thu, 07 Jul 2011 19:48:38 +0200

@Christian
https://wiki.php.net/rfc/traits

@author
Sure traits are going to make their way in. 5.4 alpha now supports traits.

Christian: Traits for PHP

nospam@example.com (Christian) — Mon, 04 Jul 2011 20:26:42 +0200

What are "traits". what is it good for? Any links?

Thanks

Rasmus Schultz: My wishlist for PHP 6, pt3: Annotations

nospam@example.com (Rasmus Schultz) — Wed, 18 May 2011 14:19:35 +0200

I love annotations! This post was one of the many I referenced early on, when I started designing my own library.

In my opinion, the mistake made by you and countless others, is to invent new syntax. Although your syntax is closer to standard PHP-DOC syntax than some libraries, you've added custom syntax for properties and values.

PHP has (familiar and readily available) syntax for that already. Okay, so you saved a few keystrokes - but you lost all of your standard PHP language features. The only new syntax you should need, is @name... everything you're trying to do between the parentheses, PHP already has syntax for - and the rest is PHP-DOC, an already well-defined, widely accepted and broadly supported standard, plus a pair of parentheses.

Have a look at my project's Wiki for more information:

http://code.google.com/p/php-annotations

Frank: vfsStream 0.8.0 released

nospam@example.com (Frank) — Tue, 17 May 2011 21:06:06 +0200

Hello PEM,

as you might guess from the long time since your comment I'm currently very busy and didn't had any time to check the issues. I'm very sorry, but I hope to get back to vfsStream in the near future.

Rasmus Schultz: State of annotations in the PHP world

nospam@example.com (Rasmus Schultz) — Tue, 17 May 2011 00:57:15 +0200

I've released my own annotation framework for PHP, and it is now stable - have a look:

http://code.google.com/p/php-annotations/

It's early days for this project still - although the framework itself is stable and complete, there is still a lot of documentation to be written, and I am planning a library of standard annotations.

There is no place for discussion yet, but you're welcome to submit bug reports, or comment via email.

Thanks!

PEM: vfsStream 0.8.0 released

nospam@example.com (PEM) — Mon, 11 Apr 2011 11:48:53 +0200

Hello Frank,

Any news on the matter ?

Marcelo Gornstein: State of annotations in the PHP world, revisited

nospam@example.com (Marcelo Gornstein) — Mon, 14 Mar 2011 13:14:08 +0100

Hello,

I've made an experimental patch to ZendEngine/PHP (5.3.5) to allow native annotations in the PHP language, the code can be found here: https://github.com/marcelog/AnoForPHP

It allows 0 or more annotations (without the use of DocComments) with 0 or more arguments themselves, in classes, methods, properties, AND arguments for methods, i.e:

/*
* The token chosen is "@@" because "@" was already taken.
*/
@@Annotation(key="value1")
class A {
@@Annotation(key="value1")
private $property;

@@Annotation(key="value1")
private function aMethod(@@Annotation(key="value1") @@Annotation2 $a, $b) {
...
}
}

I plan to use this same patch for Ding, which currently supports annotations but from standard doc block comments.

Regards!

anehra63: Dependency Injection for static methods

nospam@example.com (anehra63) — Wed, 10 Nov 2010 08:33:02 +0100

thanks for posting

neo: Dependency Injection for static methods

nospam@example.com (neo) — Wed, 10 Nov 2010 06:38:39 +0100

Surely that gives you a better interface.

Frank: Dependency Injection for static methods

nospam@example.com (Frank) — Mon, 08 Nov 2010 19:31:40 +0100

Of course you could do that, the question is if it is worth the additional work if the only purpose is to decouple for better testability.

Andy Till: Dependency Injection for static methods

nospam@example.com (Andy Till) — Mon, 08 Nov 2010 17:59:16 +0100

Why don't you just pass an object in and call methods on it, making sure you don't make those methods static. If those methods are static and you can't change the source then wrap them in an object.

Surely that gives you a better interface.