User contributions
Jump to navigation
Jump to search
- 07:02, 20 October 2007 diff hist −16 m Code Sizer update the link back to this page from the code example, now that this page is Code Sizer rather than Talk:LSL Script Efficiency
- 06:58, 20 October 2007 diff hist −14 Hex →Clever & Fast: change towards NPOV -- to "cleverly" from "confusingly" and "astonishingly"
- 06:48, 20 October 2007 diff hist +342 m Talk:Hex Complete! You can see I posted my guess of the plan of corrective action that you mean to suggest.
- 06:47, 20 October 2007 diff hist +208 Talk:Hex →Why bother with fast or small or different code exemplars: modified towards NPOV to claim value for clever as well as value for brief, clear, small, and fast
- 06:39, 20 October 2007 diff hist +425 Talk:Hex →Different & Clever & Fast: perhaps by NPOV we should implement the code yet again, without necessarily making the article even longer
- 06:37, 20 October 2007 diff hist +9 m Hex →Alternatives: clarify to "unsigned 0x80000000" from 0x80000000
- 06:34, 20 October 2007 diff hist +9 m Hex →Design Rationale: same tiny step towards NPOV -- more parallel English
- 06:32, 20 October 2007 diff hist +9 m Hex →Clever & Fast: another tiny step towards NPOV -- more closely parallel the →Clever & Small: English
- 22:57, 19 October 2007 diff hist +4,916 Talk:Hex →Third Talk: answer the talk at →18 October Rewrite: and answer the talk at →Loop Costs Unscientific
- 22:10, 19 October 2007 diff hist +400 N Talk:LlGetTimestamp Talk:Hex suggests that we should point away from llGetTimestamp over to llGetTime instead, for more accurate measure of elapsed run time when time dilates. -- ~~~~
- 22:03, 19 October 2007 diff hist +23 LlGetTime clarify to "seconds and fractional seconds" from the misleadingly brief "seconds" that can mean counting only whole seconds
- 22:02, 19 October 2007 diff hist +23 m LlGetAndResetTime resynch with recent changes to [llGetTime]]
- 22:00, 19 October 2007 diff hist +240 m LlSetTimerEvent clarify to "the time delation (lag) reported by llGetRegionTimeDilation" from "time dilation (lag)" with time dilation linked thru to llGetRegionTimeDilation etc.
- 21:52, 19 October 2007 diff hist −17 LlResetTime synch with old content and recent changes at llGetTime
- 21:42, 19 October 2007 diff hist −4 m LlGetAndResetTime unbold the self-reference llGetAndResetTime
- 21:41, 19 October 2007 diff hist +255 Talk:Code Racer Talk:Hex suggests that we should tweak this instrument to call llGetTime rather than llGetTimestamp, in order to more accurately measure elapsed run time when time dilates
- 21:40, 19 October 2007 diff hist +220 N Talk:Efficiency Tester Talk:Hex suggests that we should tweak this instrument to call llGetTime rather than llGetTimestamp, in order to more accurately measure elapsed run time when time dilates
- 21:23, 19 October 2007 diff hist +331 LlGetAndResetTime synch with old content and recent changes at llGetTime
- 21:19, 19 October 2007 diff hist +2 LlGetTime add sim reset to the list of events that reset this llGetTime dilated measure of elapsed run time
- 21:17, 19 October 2007 diff hist +12 LlGetTime politely convert the first mention of llGetTimestamp here into a link
- 21:08, 19 October 2007 diff hist −10 m LlGetTime retire the LSLG tags as I mis/remember my fellow editors advising me before
- 21:04, 19 October 2007 diff hist +188 LlGetRegionTimeDilation wild guess - guess the effect of llGetTime is "correctly slows", also link back to the timer event that already links here, also suggest llGetTimestamp for calendar time
- 21:02, 19 October 2007 diff hist +34 LlGetRegionTimeDilation wild guess -- clarify to "between 0.0 (infinite dilation) and 1.0 (no dilation)" from "between 0.0 and 1.0"
- 20:48, 19 October 2007 diff hist +262 LlGetTime guess that "also affected by" meant correctly slowed by time dilation, whenever llGetRegionTimeDilation returns a value other than exactly 1.
- 20:33, 19 October 2007 diff hist +47 m LlGetAndResetTime link with llGetRegionTimeDilation
- 20:32, 19 October 2007 diff hist +47 m LlGetTime link with llGetRegionTimeDilation
- 19:04, 19 October 2007 diff hist −1,840 m Talk:Hex propose an agenda for our →Third Talk
- 18:43, 19 October 2007 diff hist +11 m Code Sizer clarify to "neither clever nor fast nor small" from "neither fast nor small)
- 18:33, 19 October 2007 diff hist +1,150 m Talk:Hex →18 October Rewrite: explain my progress so far, and say good bye til I can return, soon I hope
- 18:24, 19 October 2007 diff hist −180 Efficiency Tester link directly with Code Sizer -- was merely alluding cryptically to the brief & clear & conventional (though neither small nor fast) harness for llGetFreeMemory that that article now presents
- 18:23, 19 October 2007 diff hist +135 m Code Racer →See Also: link with llGetTimestamp
- 18:21, 19 October 2007 diff hist +108 m Code Sizer →See Also: link with llGetFreeMemory - count bytes of code plus heap plus stack spent by the script as yet
- 18:21, 19 October 2007 diff hist +272 Code Sizer link with Code Racer and Efficiency Tester, also add LSL Library and LSL Examples links by membership in those categories
- 18:18, 19 October 2007 diff hist +211 Code Racer link with Code Sizer - count bytes of code, and link with Efficiency Tester - count milliseconds of run time
- 18:14, 19 October 2007 diff hist −3,127 Talk:LSL Script Efficiency archive the talk that gave birth to the Code Racer article current
- 18:09, 19 October 2007 diff hist +144 Talk:Hex disentangle the presentation of raw byte count size data from the presentation of raw milliseconds run time data and link with Code Sizer
- 18:06, 19 October 2007 diff hist +122 Hex →Measuring Concise & Conventional & Small & Fast: link with the Code Sizer article
- 18:03, 19 October 2007 diff hist +2,222 N Talk:Code Sizer add one section to guess how the plus four instrument, add one section to blog the design rationale behind the Code Sizer instrument
- 17:56, 19 October 2007 diff hist +2,184 N Code Sizer answer Q: Want to know how small that code is?
- 17:54, 19 October 2007 diff hist +113 Category:LSL Library add Code Sizer - count the bytes compiled from source code, to measure how to write small code.
- 17:41, 19 October 2007 diff hist +3,282 N Talk:LSL Script Efficiency propose an article to show how best to call llGetFreeMemory to measure how small is that code
- 17:03, 19 October 2007 diff hist +71 m User:Ppaatt Lynagh →Thanks: to Thraxis for introducing me to the <nowiki>__TOC__</nowiki> tag at hex.
- 17:02, 19 October 2007 diff hist +162 m User talk:Thraxis Epsilon And thank you for explaining the <nowiki>__TOC__</nowiki> tag that the hex page needed.
- 15:47, 19 October 2007 diff hist +651 m Talk:Hex →Edit Conflicts: mention the edit conflicts, hope no one hurt →197 bytes or more: add place to guess of how best to get consensus on how to measure bytes of code
- 15:36, 19 October 2007 diff hist 0 Talk:Hex →Loop Costs Unscientific: which procedure for reproducing loop cost results should we publish
- 15:34, 19 October 2007 diff hist +533 Talk:Hex →Loop Costs Unscientific: which procedure for reproducing loop cost results should we publish
- 15:32, 19 October 2007 diff hist +1,237 Talk:Hex →18 October Rewrite: Hex#Measuring_Concise_.26_Conventional_.26_Small_.26_Fast gives procedure for reproducing bytes of code and milliseconds of run time
- 14:53, 19 October 2007 diff hist +328 Talk:Hex →18 October Rewrite: good news, we have hate and hate, well balanced
- 08:31, 18 October 2007 diff hist +10 m Code Racer clarify to Alternatives & Caveats from Alternatives
- 08:28, 18 October 2007 diff hist +2 m Code Racer clarify to Instructions from Discussion