Jump to content

Love Zhaoying

Resident
  • Posts

    34,799
  • Joined

  • Last visited

  • Days Won

    172

Everything posted by Love Zhaoying

  1. My favorite part!!! Thanks for the details. Too bad there's no mutable string. One nice saving grace is local variables.
  2. Pet peeve: Witty things that you want to say regarding light and shade, but have to redact due to common sense self-filtering. Oh great, now I have a cheesy 90's song about "Lights and Shadows" stuck in my head! ~~ PEEVED ~~
  3. I am seeing reminders on my Facebook that I adopted this pair 4 years ago! Time flies, but it feels longer also. Meaning: I can barely remember them not being in my life.
  4. The best thing about an interpersonal dispute is, the make-up nookie! ("I love it when we fight!")
  5. Yeah, "naming and shaming" is not allowed. Too bad.. Can you not even name others in your in-world profile, then refer people to "go read my profile for details"? Last I remember, no.
  6. Like Rolig said: Most common rezbox systems require you to put a script in each object, touch each object and the box to "lock" its position, and THEN put each item into the box. Only then each object "know" its position (from the script)..and the box will know about the objects..
  7. Got a new harness for the big boy today, 40" chest!
  8. I think, that there is a LOT to do in Second Life. However, Second Life is so big, and spread out, with empty spaces (spaces with no other avatars), that it can be hard to "find" things to do. Especially if you're new. Because of this a lot of suggestions (mine included) are for things like "improved guides", etc.
  9. Does that mean that lists may be able to take advantage of "split" memory / be more GC relevant? That could explain some stack-heap collisions used by large strings.. I can see implementing strings without using non-contiguous memory blocks, since a string is usually "contiguous data". They COULD have implemented it with non-contiguous blocks, of couse but if they didn't.. Anyway, thanks for the information!
  10. Could it be that this is one of the first functions to be "offloaded" in this specific way? That could explain the different behavior (with timing).
  11. Peeve: Spent an hour changing a script to behave differently ("process all" vs. "process one and wait for command") and only saved 1 second in processing time. On the plus side, it was a 7% savings!
  12. Awesome analysis! I am confused however, by the above snippet. With 250 entries vs. 50 entries, it took longer for strings (5.7x), than for lists (5.3x)? But for 50 entries, it took longer for lists, than for strings? Thank you!
  13. Were it closer to Halloween, it would seem more normal to carry a "dead baby" around declaring to all, "my baby is dead"! I hope you find a new baby to your liking.
  14. I suspect you'll find that strings are faster than lists and use less memory. But in this example, since you're just building and dumping, not searching and manipulating a list, the difference could be trivial. I suppose my "rule of thumb" is, "did I need to use a list, when I could have used a string or JSON?"
  15. My feeling from this thread is, it's "just so", because it should be "obvious", due to the "very definition of classicism". All these are very poor arguments. "Obviously", those who may disagree are wrong. Right?
  16. It seems to me, that "roads", which on Mainland are generally Public access, may be a somewhat obvious way to avoid this issue. Just a thot.
×
×
  • Create New...