|Squeak Everyday||http://propella.blogspot.com/atom.xml||Tak's blog|
|ESUG||http://www.esug.org/?action=RSSChangesFeed||European Smalltalk User Group|
|SqueakSource: SqueakSource all projects RSS feed|
|Kernel.V3-dtl.1202: Name: Kernel-nice.1202|
Time: 12 December 2018, 12:31:18.370647 am
Ancestors: Kernel-pre.1201, Kernel-nice.1200
Merge Kernel-pre.1201 + Kernel-nice.1200
Time: 9 December 2018, 11:17:42.830548 am
Let's make basicInspect robust to crazy numbers.
I can create crazy numbers like this:
((1 asArbitraryPrecisionFloatNumBits: 100) timesTwoPower: 1e100)
But then I can't print to decimal form (a bit too many bytes to be allocated....).
The problem when debugging such monster is that basicInspect is not basicEnough: it insists on printing the Number in the inspector title (label)!
If we invoke basicInspect, we generally want something basic. Even if we just inspect, having a label spanning more than 100 chars is vain...
So let's be robust.
|Kernel.V3-dtl.1201: Name: Kernel-pre.1201|
Time: 10 December 2018, 8:25:07.937104 pm
Adds the classifyAllUnclassified method to ClassOrganizer. The method name remains consistent with the classify* methods of organizers. Further recategorizes some methods from accessing to classifying
|Kernel.V3-dtl.1200: Name: Kernel-fn.1200|
Time: 10 December 2018, 11:04:26.031004 am
Fix WeakMessageSend's class comment.
|Kernel.V3-dtl.1199: Name: Kernel-eem.1199|
Time: 24 November 2018, 3:19:28.081135 pm
Remove a mistaken halt from the postscript of the previous commit.
|Kernel.V3-dtl.1198: Name: Kernel-eem.1198|
Time: 24 November 2018, 1:44:47.526422 pm
Redefine LargePositiveInteger hash for compatibility between 32-bit and 64-bit systems.
|Kernel.V3-dtl.1197: Name: Kernel-eem.1197|
Time: 20 November 2018, 1:43:36.839917 pm
Define #= and #hash for Message such that distinct Messages with the identical selector and lookupClass, and literalEqual: arguments are equal.
|Kernel.V3-dtl.1196: Name: Kernel-eem.1196|
Time: 20 November 2018, 1:39:00.487858 pm
Fix ClosureExtractor (embeddedBlockClosures) for exotic Sista blocks.
|Compiler.V3-dtl.396: Name: Compiler-eem.396|
Time: 20 November 2018, 1:34:47.963843 pm
Fix a slip in Sista block creation
|System.V3-dtl.1047: Name: System-pre.1047|
Time: 20 December 2018, 1:56:15.427193 pm
Categorizes uncategorized methods in the System category.
|Files.V3-dtl.182: Name: Files-pre.182|
Time: 11 December 2018, 3:28:52.883299 pm
Ancestors: Files-nice.163, Files-tpr.181
Recategorizes methods in the files package. Also moves a deprecated method into the corresponding deprecated extension category.
|Collections.V3-dtl.811: VM note - primitives 165 and 166 fail in interpreter VM, though this is functionally harmless so the updates are applicable for V3 with any VM.|
Time: 31 October 2018, 10:44:24.941583 am
Use the integerAt[Put] primitive to implement signedByteAt:[put:]
|Collections.V3-dtl.810: Adopt Collections-ul.810 but do not override #hashWithInitialHash in ByteArray or ByteString for V3.|
Time: 30 October 2018, 1:26:22.149414 am
- renamed the methods #stringHashWithInitialHash: and #bytesHashWithInitialHash: to #hashWithInitialHash:
|ConfigurationOfXMLRPC-sg.22: empty log message|
|ProjectQuinto: Juste pour le plasir|
|w00t: Here it goes...|
|Dead Code Detection - Group 6 - Week 1: We were able to import *.mse files successfully and started to think about how we could detect dead code. After browsing through the moosetechnology.org website, we saw that one possibility would be to use the methods provided by Moose Chef to handle dead code detection. But since this is all new to us we would like to be sure that we're not starting off from the wrong foot. Could you please tell us if using Moose Chef would be a good approach? Thank you.|
|Dead Code Detection - Group 6: Test|
|A database driver for MySQL protocol: The driver is now capable of authenticating users in case the password was created in old style (short hash). The new style (long hash) password support remains available as usual. The fallback is silent, and handled during the handshake. Similar mechanisms apply to change user command.|
In order to test the short has password cases change the password to use the old style by issuing commands like (from an admin account):
set password for 'stdbtestuser'@'%' = old_password('stdbtestpass')
Then run the test suite.
To change the password style back to new hash just do:
set password for 'stdbtestuser'@'%' = password('stdbtestpass')
Then run the test suite again to confirm.
|SBE Quinto Game: hmm, test: add message|