![]() Microsoft made a stupid, stupid change to command line parsing that impacted link() and caused incorrect results on many systems where the default browser was Chromium-based.json_decode() could crash for some inputs.The fix for launching links in the default browser had a bug for certain links.Raw strings did not get parsed correctly when included in macro arguments.Another aspect of the link() fix was apparently incompatible with multiple websites.VIS_UNDERLAY could sometimes propagate further than intended.Turfs in visual contents of objects did not properly mark when they were no longer in use (on the client) as a result of the obj or mob being deleted.A second animate() call with the parallel animation flag could sometimes temporarily show out-of-sync results, such as the new animation appearing to be at its endpoint for a single frame before running the rest of the animation normally.Applying a color to an atom with maptext did not necessarily apply the color to the maptext also, if the color was opaque. ![]() operator on the left-hand side of an assignment operator worked incorrectly in certain cases when adding/assigning some constant values such as negative numbers. The compiler allowed vis_locs and vis_flags to be defined under /image these vars are only relevant to turfs and movable atoms.Including a raw string (any format starting with in a block of code skipped by a preprocessor directive would cause compilation to proceed incorrectly.When reading the length of client.verbs directly, a value of 0 was returned.flist() failed in Windows on directories with trans-ASCII characters in their names.operator caused problems when it was used in certain expressions. Maptext underlines appeared in the wrong position when the map drawing area was bigger than the control itself, e.g.#define macros that used strings with embedded expressions were parsed incorrectly when the substitution was made.Escaped line breaks in #define macro arguments were handled incorrectly. ![]() and ?: operators were compiled incorrectly when used in left-hand-side expressions, which resulted in weird errors at runtime. replacetext() can now allow negative index values for the start position. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |