Library: Object Radar

You still do not get it and from your attitude you never will. So let's just be upfront and clear; Stay away from threads started by scripting noobs and try picking on the scripts of some of us older members instead. I see a lot of talk but haven't seen you posting any of your work here. That is how you teach, by example not by criticizing the work of others.

as the old net thingy goes QFT!

oh, I am still doing Sl, I have long since improved my scripting ability.
yes,I was new to scripting, so mistakes are there.
and I say, you went off topic pretty badly...but thanks for the tips.
and I dont mind the flames, they keep me toasty and give me advice.
I continue to release just generally useful scripts, free to the public, simply for the good of the internet (and my own desire for underground fame)

Definitely glad to see you still around and contributing!

As a side note, there is no such thing as an *official* LSL wiki, not even the one at wiki.secondlife.com.

Wow why does Linden Lab has to suck so much? I mean the concept of Second Life is cool, but wth, documentation of client is practically non-existent, and no official specification/documentation of LSL? It's like Second Life is some dude's home project

well it is pretty open source now days. you can have private servers that run different languages i hear. not too keen on that kind of scripting, but hey.
and yes, it sucks not having proper documentation, but we are a large community of smart people, and we seem to be figuring it out on our own pretty well.
plus, lindens dont suck at everything in my opinion, i think they just are normal people who have alot of stuff on their plate.

Well, they get tons of money, why cant they implement it in a sane way? The should hire some real programmers and optimize the shit out of their servers and roll out documentation that actually makes sense and is consistent with reality.

Regardless of why you think it's a substandard script or why you feel that the OP was acting overly proud, for you to feel compelled to voice insults just demonstrates that you are capable of acting like a pompous ass.

Without exception, every programmer/scripter has written code that they could later improve upon, and there's nothing wrong with feeling satisfied about your current level of progress and wanting to share that with others.

I applaud the original poster's desire to give to others.

I have a problem getting this to work. I made sure I copied the exact code but nothing happens when I exit

Just tested as posted and it works just fine. Do you understand the script and did you touch the object it is in?

Argent is correct.

The thing to keep in mind about the difference between ++x and x++ is that the former returns the incremented value and the latter does not. This seems like a small matter, but in object-oriented code, if the object being incremented is expensive to create, it matters a LOT.

You see, with ++x, we increment the object, and use its value.

With x++, we have to create a new object to hold the old value, since it's returned. Yet, in this case, we don't even use the value.

In C, the difference between the two is minimal and easily optimized out.

In C++, when x is an object, the semantics require creating the duplicate object even if its value isn't used, if creation might have any side effects. No doubt there are cases where creating the duplicate value can be optimized out by the compiler, but frequently it can't. Frequently, the compler can't see the constructor implementation, so it must invoke it.

So, if you're not going to use the pre-incremented value, use ++x, not x++. I suggest you just get in the habit of always using ++x, and only use x++ if there's a reason for it -- and in that case, remember to ask yourself about the ramifications of creating a copy of the pre-incremented value.

I suspect this is true of any language that supports the "++" operator, and most expecially, object-oriented ones.

In LSL integers are passed around as 32-bit values on a stack, no object is created.

Agreed, Argent. I still think my advice to use "++ix" by default is good advice.

In any case, testing shows that ++ix is faster than ix++ for old LSL.

default
{
    state_entry()
    {
        llOwnerSay("ready");
    }

    touch_start(integer total_number)
    {
        integer ix;
        float   t1;
        float   t2;
        
        llResetTime();
        for (ix = 0; ix < 10000; ++ix) {
        }
        t1 = llGetTime();
        
        llResetTime();
        for (ix = 0; ix < 10000; ix++) {
        }
        t2 = llGetTime();
        
        llOwnerSay((string)(t2 - t1));
    }
}

Consistently prints positive numbers (about .. Exchanging ++ix and ix++ consistently prints negative numbers of the same magnitude.

I don't remember who it was who told us that the byte code for ++ix is less than for ix++. If asked, I would have said it was probably you.

I can't measure any difference between the two for Mono.

sometimes it's useful to get the current value, instead of the already incremented value, depending on the program logic (which I habitually forget to and write around it with --x)