You are, of course, correct. If your itype does not reference the id field of the record, then I do not necessary to assign @id.
My bias towards always assigning it comes from experience writing utilities, where no such assumptions may be made, rather then writing code dependent on the individual's knowledge of each DICT item. One other note: you may some day encounter an itype that alters @id or @record during execution, so it is best to set them before each call, not counting on them to be static between multiple DICT item evaluations. -Rick On Jan 10, 2010, at 8:31 AM, Anthony W. Youngman wrote: > In message <[email protected]>, Rick > Nuckolls <[email protected]> writes >> I doubt that I will be the only one to reply, but.... >> >> The variables "@id" and "@record" must be set prior to the call, as in: >> > Note that both of these are *optional* *if* they aren't used. > > But it's extremely unlikely you won't use at least one of them. I don't > think I've ever bothered with @id, just so happens that's the way the > i-types I've used have panned out. > > Cheers, > Wol > -- > Anthony W. Youngman <[email protected]> > 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the > thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man > lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 > Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
