#new version #basicNew when materializing (SIXX/Fuel difference)
Hi guys, I found this a bit strange and arguable. Upon materialization, for normal classes, Fuel uses #basicNew to instantiate objects and then sets its instances variables values getting them from the stream.... Today I found that SIXX sends #new first (*and hence #initialize is sent*) and after, if fails, it tries, #basicNew. This 2 approaches have different results. Which one would you expect? -- Mariano http://marianopeck.wordpress.com
On Thu, Feb 27, 2014 at 5:29 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Hi guys,
I found this a bit strange and arguable. Upon materialization, for normal classes, Fuel uses #basicNew to instantiate objects and then sets its instances variables values getting them from the stream....
Today I found that SIXX sends #new first (*and hence #initialize is sent*) and after, if fails, it tries, #basicNew.
This 2 approaches have different results.
Which one would you expect?
Yours. SIXX's approach is doing unnecessary work. Answer it another way. Have you found any cases where using basicNew[:] leads to errors? If not, then it is the better approach because it is more efficient. -- best, Eliot
participants (2)
-
Eliot Miranda -
Mariano Martinez Peck