what should get returned? an error? an array of nils (like .extend(5))?
The latter makes sense to me... let me know what the rest of you think.
On Jan 6, 2008, at 1:15 PM, James Harkins wrote:
On Jan 6, 2008, at 3:19 PM, James Harkins wrote:
1843401 sclang crash on invalid code - I'm going to split 1843401 into separate issues, one for the original problem -- v() crashes the compiler -- and another to look for array primitives that don't check for empty arrays. I might be able to look at the array problem. The compiler issue... I have no idea... possibly only jmc knows the compiler well enough to fix it?
I opened issue 1865286 for the array problems.
I added array size checks to prArrayEnvAt, prArrayAtIndentityHash and prArrayAtIndentityHashInPairs to avoid invalid object returns. If the array is too small for a valid calculation, returns errFailed.
Remaining to fix:
.wrapExtend(5) -- fills array with bad objects
.clipExtend(5) -- same
.foldExtend(5) -- same
.lace -- crashes
I'm not familiar enough with pyrite object creation / gc / etc. to fix these. I checked all the array primitives I could find and the others are ok.
: H. James Harkins
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
Sc-devel mailing list
/* Joshua D. Parmenter
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono*/