But why don't you join the 1st and 2nd parameter into a unique one?
Doing a typecheck will lead to one behavior or other.
I find adding 2 parameters that do the same in a function is overcharging
it, that's why I suggested to keep both setEventMessage and
setEventMessages.
If i join into a single parameter i can't provide both the string
-error and the parameter -errors into one call.
2014-11-04 12:42 GMT+01:00 Marcos García marcos...@gmail.com:
But why don't you join the 1st and 2nd parameter into a unique one?
Doing a typecheck will lead to one behavior or
Why would you want to add both a string and an array of errors into the
same call?
That's weird from my point of view...
Regards,
*Marcos García*
marcos...@gmail.com
2014-11-04 17:50 GMT+01:00 Destailleur Laurent e...@destailleur.fr:
If i join into a single parameter i can't provide both
Raphael thank you for this synthesis
There actually is a problem of manpower for testing and probably more time will
not change. It prevents many of us to look after our customers and finaly run
out of time to work on the core.
This is due that we stay between developers, or Dolibarr users
charles...@benke.fr a écrit le 05/11/2014 00:13 :
The establishment on an visible RC version (in the .fr and .org website) will permit
users (not necessarily developer) to test more in depth version of this qualification and return
faults detected. This is probably also to us to educate our
