|
"Walden H. Leverich" wrote: > > >Danger, danger. You don't always get an exception if you reference an > >unpassed CLLE parameter. > > Um, sorry, but that leaves lots of open territory -- what's the concern? > If I had the time I'd go try it now, but I don't. > Fair enough, but whatever it updated _has_ to be in the current jobs > memory space, no? Or is there where the flat address spacing is coming > to bite us. > > Spill the beans Barbara, what are you worried about? > No beans to spill. I always worry about random storage corruption, and I don't think it's ever a good idea to deliberately induce it unless you know exactly what storage you will corrupt. I don't know that anything particularly nasty will happen if you run this program - I really don't have any idea what got updated when I made that first call. Even if the storage that it updates is in the current job's memory space, are you really willing to poke a stick randomly into your job and stir it around?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
