Hi Joep,
2011/4/27 Joep Suijs <[email protected]> > > > It's particularly hard to implement this with efficiency > > without pointers. > Why is that? Since you need dynamic memory allocation for a changing > mix of datatypes? > If the mix of datatypes is fixed, you could use arrays. > I'm not sure about you mean, but I'd need references in order to pass easily pass inode records. One inode record weighs ~ 80 bytes, passing them to procedures costs too much. And storing them within an array really costs a lot of resources when accessing them. > > > I extensively use "record" > Nice. I assume it works like it should even in this beta-version? > As far as I could see, it works pretty well and really helps having an clean code. This only new issue I could find, which I reported to Kyle via jallist, was when a record stores an array, and you want to access this array like in: for count(the_record.the_array) loop ... en loop another older "issue" is it's not possible to alias a record variable: alias bla is the_record.bla Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
