On Sun, 2013-07-14 at 12:39 +0200, Sebastian Krebs wrote:
Backward compatibility (or compatibility in general) between component
is something the plugin maintainer should take care of, not the
language.
Ack. If a library becomes incompatible one should change the name or
namespace or
Am 15.07.2013 11:14, schrieb Johannes Schlüter:
Besides the pure compatibility issue traditionally we also had a
distribution problem in PHP - if a module requires a generic library
either the library had to be bundled or the user had to be sent for a
hunt and manually do it, which became
On Mon, 2013-07-15 at 12:07 +0200, Sebastian Bergmann wrote:
Unless I missed a corresponding feature so far, Composer does not
solve
this problem. This problem could be solved, however, by encoding the
version number in the namespace name:
I didn't say composer solves that part, for
On Sun, Jul 14, 2013 at 12:13 PM, Giuseppe Ronca
giuseppe.ron...@gmail.com wrote:
Php is now used by many CMS, many of which use a modular system with a wide
range of add-ons developed by third parties. This can cause various
conflicts, such as when two or more external components using the
-- Forwarded message --
From: Giuseppe Ronca giuseppe.ron...@gmail.com
Date: 2013/7/15
Subject: Re: [PHP-DEV] PHP proposal on modular systems
To: Johannes Schlüter johan...@schlueters.de
I'm not talking about this kind of problem...
I think you know how a CMS works ... we've for
On 15 July 2013 16:51, Giuseppe Ronca giuseppe.ron...@gmail.com wrote:
I'm not talking about this kind of problem...
I think you know how a CMS works ... we've for example :
* *CMS sources that are developed by Joomla devs ( i.g ) with theirs
libraries.*
* *Plugin (A) developed externally
Marco Pivetta wrote:
PS i'm not so practice with composer ( used few times ) but when modular
systems , such as CMS , give the possibility to extends them with external
components...i don't think that composer could solve this problem.
It is actually already happening.
You should really
Am 15.07.2013 18:24, schrieb Lester Caine:
Marco Pivetta wrote:
PS i'm not so practice with composer ( used few times ) but when modular
systems , such as CMS , give the possibility to extends them with
external
components...i don't think that composer could solve this problem.
It is
2013/7/15 Lester Caine les...@lsces.co.uk
Marco Pivetta wrote:
PS i'm not so practice with composer ( used few times ) but when modular
systems , such as CMS , give the possibility to extends them with
external
components...i don't think that composer could solve this problem.
It is
I've studied Composer and as i thought ..it's a component installer
(implementing an autoload system) .. nothing else ( i can have similar
result using git submodules )
anyway , *you can have a class collision using or not using composer ( it
doesn't solve it, but just advise you that you can't
You can have multiple objects from the same type in different
implemenations in the same process?
No i'm not saying it.
What should happen, when I instanciate an object of test in version X and
pass it to a function, that expect it as version Y? To be consistent PHP
_must_ trigger an
11 matches
Mail list logo
