> On 16.03.2015, at 15:45, Theodore Brown wrote:
>
> This is a bug in the library. It declares strict mode but passes a value it
> does not know to be an integer to a method requiring an integer. It can
> be fixed by simply adding an int type declaration to the constructor or
> test method.
It
Hey,
> This is a bug in the library. It declares strict mode but passes a value it
> does not know to be an integer to a method requiring an integer. It can
> be fixed by simply adding an int type declaration to the constructor or
> test method.
The second example is certainly a programmer error,
On 16/03/2015 14:45, Theodore Brown wrote:
On Monday March 16 at 9:33 am Thomas Punt wrote:
Strictly speaking (pun intended), this is not true. A library can easily expose
a
facade that enforces a user of that library (who is in weak mode) to have to
write
in strict mode [1]. Once more, this
On Monday March 16 at 9:33 am Thomas Punt wrote:
> Strictly speaking (pun intended), this is not true. A library can easily
> expose a
> facade that enforces a user of that library (who is in weak mode) to have to
> write
> in strict mode [1]. Once more, this can be done unintentionally [2] beca
