Jon, project, note 3

[Ruslan Zasukhin]

Hi Jon,


Another logical mistake in your project is that you create Method

Table_CreateTextField...
    PARAM: inTable = 4071720
    PARAM: inName = "titleMethod"
    PARAM: inType = 24
    PARAM: inFlags = 8
    PARAM: inMethod = "Upper(editors)"
return object = 26901888

 
That refer to field "editors", which is create LATER !


In fact this is not good idea.
In most programming language you need declare something BEFORE you will use
it.


Yes, Valentina 1.x was able resolve this,
Payment for this was the second scan of all fields and attempt again compile
bad methods. But this is waste of time. Right?

In Valentina 2.0 we did not have such mechanim yet, so your project did fail
here also. For now I have made just protection from crash.
And I will need made again second iteration.

I will try to do this that iteration happens ONLY if there was bad method.
I.e. In case developer have made all right, we will not waste time as
Valentina 1.x did this.



-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------