Re: faux-namespacing of SimpleTest (was: Re: Two Things)

Oliver Saunders wrote:
> Yeah that is the nice thing about PEAR naming, if you
have the class
> name you immediately know where to go to find it's
definition. That
> does makes things like __autoload() or name based
dependency injection
> exceptionally easy to implement. Although there are
disadvantages and
> moving over to it would be a huge task. So I wouldn't
recommend it for
> SimpleTest
>   

Agreed and agreed... 


> Would backward compatibility be a problem? Considering
that you could
> provide SimpleTest users with a script or two to update
their code. I
> would happily write those. bash and cmd are probably
easiest
> considering their close ties with the filesystem and
they can just be
> run with a starting path arg without needing
installation.
>   

This would actually be the main reason for using something
like that 
<addnamespace> phing task to handle injection.  It
would allow for 
packaging of both versions of the code to maintain BC.  We
could 
deprecate UnitTestCase in favor of ST_UnitTestCase, but
still have the 
BC package available.  As long as we don't modify the file
location, it 
wouldn't be hard to strip out namespaces using phing and
their 
<replaceregex> task.

-Travis

------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Simpletest-support mailing list
Simpletest-supportlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simp
letest-support

Hi...

Travis Swicegood wrote:
> We could 
> deprecate UnitTestCase in favor of ST_UnitTestCase, but
still have the 
> BC package available.

UnitTestCase is not going to cause a name clash in the next
million
years. Prefixing it is pointless, and just makes the code
look cryptic.

Don't forget that the main design driver for SimpleTest is
the
tutorials. Anything that weakens those reduces the number of
people that
will start unit testing. The whole reason for the project
was to make
unit testing, mock objects and acceptance testing more
widely known.

With TextReporter however, you have a point .

Moving over to autorun as the default makes use of this
class name much
less routine. Certainly it could become SimpleTextReporter
on a
deprecation cycle.

> 
> -Travis

yours, Marcus
-- 
Marcus Baker
marcuslastcraft.com

------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Simpletest-support mailing list
Simpletest-supportlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simp
letest-support