Le 03/07/2013 11:59, Igor Stasenko a écrit :
On 3 July 2013 11:48, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Is there something against that ?
It seems as if NB is used to check file existence / isReadable, then, upon startup, the vm is unable to open the changes file and all NB calls becomes incorrect.
NB callout needs argument names (which it can only get right now by accessing method's source). We plan to change that after introducing pluggable mechanism in opal to use it to run additional code on certain pragma to handle it in custom way (like remembering argument names in method's properties).
If it is like that, I have to give up any chance of correcting the file permissions problem on Pharo 2.0. Any chance that we could use arguments positions instead ? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95