Search results

Jump to navigation Jump to search
  • ...t an explicit typecast). By changing the multiplied constants, you can get it produce lowercase characters. llIntegerToBase64(
    4 KB (463 words) - 17:27, 8 November 2009
  • |func=llIntegerToBase64|return_type=string|p1_type=integer|p1_name=number return llBase64ToString(llIntegerToBase64(letter << 24));
    2 KB (251 words) - 11:37, 11 October 2023
  • I wrote these more for the fun of it, an exercise in cleverness, than to be useful. The design goal was to not u ...rse the process, which is good. It's more costly to call the function then it is to inline the functions functionality.
    4 KB (435 words) - 13:44, 9 March 2023
  • ...cently asked for a more memory efficient version so I hacked one together. It could be made faster by using two loops, and pealing off characters in bigg return llGetSubString(llBase64ToString(llIntegerToBase64(num)), 0, 0);
    2 KB (217 words) - 09:50, 13 June 2012
  • llGetSubString(llIntegerToBase64((integer)("0x"+llGetSubString(s,0,5))<<8),0,3) + llGetSubString(llIntegerToBase64((integer)("0x"+llGetSubString(s,6,11))<<8),0,3) +
    5 KB (568 words) - 17:04, 5 February 2015
  • ...This is what llBase64ToInteger and llIntegerToBase64 are good for. Suppose it's time I post some of the new functions to the Combined Library. -- [[User: ...anged the code to use the llBase64ToInteger and llIntegerToBase64 methods. It is a lot smaller and easier to manage now. --[[User:Dedric Mauriac|Dedric M
    3 KB (540 words) - 00:10, 3 December 2013
  • ...o impress upon you that the logic of your implementation is not only sound it is pretty efficient. ...the string then just doing it all at once to a single integer. I'd rewrite it as:
    2 KB (327 words) - 11:17, 6 January 2010
  • ...ing|inline=*|Security|The MD4 hashing algorithm should not be used because it is too easy to generate collisions (two inputs which result in the same has ...gs in LSL are UTF-8) and the other is for Base64 Strings (you need to tell it how many bits long the data is).
    9 KB (1,073 words) - 17:17, 24 January 2015
  • ...ing|inline=*|Security|The MD5 hashing algorithm should not be used because it is too easy to generate collisions (two inputs which result in the same has ...gs in LSL are UTF-8) and the other is for Base64 Strings (you need to tell it how many bits long the data is).
    12 KB (1,391 words) - 17:18, 24 January 2015
  • ...stuff and seems to work. Keep in mind LSL doesn't allow \0 as a string, so it may still be secure but might not work with other libraries. result = result + llBase64ToString(llIntegerToBase64(num));
    3 KB (419 words) - 09:31, 11 July 2017
  • ...rt API]. The example here takes a list of visitors per hour and represents it as a bar chart. The simpleEncoding method provided by Google has been conve text = llGetSubString(llIntegerToBase64((integer)(range * (min - llList2Float(values, index)))), 4, 4) + text;
    3 KB (286 words) - 15:10, 24 January 2015
  • // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public License
    13 KB (1,601 words) - 16:52, 9 December 2023
  • // To use it, set your passphrase below. If you're not as worried about speed // base64 XTEA script somewhere. If you want to correct that and it doesn't
    21 KB (2,247 words) - 11:16, 25 January 2015
  • Creating textures in-world is not possible in SL, but for some tasks it is useful to be able to produce images with scripts. Such as making sculpt ...ve occurred while the script prints the image. After saving the file, open it with any web browser. The image can be saved in BMP format from the web br
    8 KB (1,055 words) - 05:01, 7 September 2015
  • ...ur option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty ...guage - that implies a useless programming language (except for the fun of it).
    6 KB (653 words) - 02:08, 23 June 2013
  • ...our bytes of common ASCII characters in a completely reversible algorithm. It is generally used to convert binary data to strings so they can be sent acr |12345 (as an [[llIntegerToBase64|integer]])
    5 members (0 subcategories, 0 files) - 23:12, 24 June 2013
  • ...t it returns "d998312450ba64589563cc563a6cc0cf", same with UTF8_MD5("666") it returns "693e9af84d3dfcc71e640e005bdc5e2e" instead of "fae0b27c451c728867a5 ::It must be something to do with the order of operations as I get the correct r
    14 KB (1,886 words) - 13:10, 11 January 2012
  • ...UIST-STIUF is an extension of FUIS-SIUF which is an extension of FUI-IUF). It encodes lists into strings and back into lists with care to restore the typ ...e Combat System and the functions were given the names "parse" and "dump". It wasn't until the development of {{HoverText|TLTP|Touch Link Transfer Protoc
    11 KB (1,406 words) - 15:11, 22 January 2015
  • ...keys into a message, especially when sending to a webiste. For this reason it may be beneficial to use key-compression, to reduce the size of keys. ...ressed key will typically be a little smaller than 50% the size of the key it represents.
    17 KB (2,144 words) - 01:43, 29 March 2024
  • if((a)){//is it nonzero? ....4012984643248170709237295832899e-45){//It should at this point, except if it's NaN
    12 KB (1,711 words) - 13:36, 14 September 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)