It's generally a bad idea to change behavior dramatically, and much
safer to add a new function.
Dramatic changes in behavior cause new bugs, or cause old but
insignificant bugs to become significant.
New functions don't.
On Sun, Mar 7, 2010 at 9:39 AM, Obsidian Kindragon
wrote:
> Hi all,
>
>
On Sun, Mar 7, 2010 at 6:58 AM, Michael Schlenker
wrote:
>
> Am 07.03.2010 um 15:39 schrieb Obsidian Kindragon:
>
>> Hi all,
>>
>> I've a quick question regarding the new llSetLinkPimitiveParamsFast()
>> function in 1.38.0. Why did LL opt for a new function instead of just
>> removing the delay fr
pile the script(s)
>>
>> GCI
>>
>>
>> - Original Message -
>> From: "Obsidian Kindragon"
>> To:
>> Sent: Sunday, March 07, 2010 3:39 PM
>> Subject: [opensource-dev] Question regarding
>> llSetLinkPimitiveParamsFast()function
ragon"
> To:
> Sent: Sunday, March 07, 2010 3:39 PM
> Subject: [opensource-dev] Question regarding
> llSetLinkPimitiveParamsFast()function in 1.38.0
>
>
> > Hi all,
> >
> > I've a quick question regarding the new llSetLinkPimitiveParamsFast()
>
[opensource-dev] Question regarding
llSetLinkPimitiveParamsFast()function in 1.38.0
> Hi all,
>
> I've a quick question regarding the new llSetLinkPimitiveParamsFast()
> function in 1.38.0. Why did LL opt for a new function instead of just
> removing the delay from the current
On 2010-03-07, at 08:39, Obsidian Kindragon wrote:
> I've a quick question regarding the new llSetLinkPimitiveParamsFast()
> function in 1.38.0. Why did LL opt for a new function instead of just
> removing the delay from the current llSetLinkPrimitiveParams()
> function?
Because code that curren
Am 07.03.2010 um 15:39 schrieb Obsidian Kindragon:
> Hi all,
>
> I've a quick question regarding the new llSetLinkPimitiveParamsFast()
> function in 1.38.0. Why did LL opt for a new function instead of just
> removing the delay from the current llSetLinkPrimitiveParams() function?
> I can't c
Hi all,
I've a quick question regarding the new llSetLinkPimitiveParamsFast()
function in 1.38.0. Why did LL opt for a new function instead of just
removing the delay from the current llSetLinkPrimitiveParams() function?
I can't conceive any case where removing the delay from the current
funct