- Pharo-users - lists.pharo.org

Re: [Pharo-users] As promised, the sequel!

by tbrunz

Exactly. I gave you a suggestion for an article. That's hardly plagiarism by any definition. Keep up the good work, Richard! You're selflessly filling a real need, and it's appreciated. -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 16, 2020

Re: [Pharo-users] As promised, the sequel!

by horrido

Getting an idea suggestion for an article is plagiarism??? I get ideas from all kinds of sources. From friends. From strangers. From television and movies. Et cetera. There's no point in citing all of them. xap wrote > tbrunz, my comment above was to pander to my own selfish views of > how-the-world-ought -to-work than for your benefit ;-) > > My own druthers would have been to refer to this list and your comments in > the para "Pharo is also extremely versatile which is well-explained in > this > article, âSmalltalk: Itâs Not Your Grandparentâs Programming Language.â" > > As it is -- to me -- it smacks vaguely of plagiarism, and is the sort of > stunt that gets one expelled -- certainly, called up to the dean -- in an > educational institution of any standing. I expect more inclusivity and > grace > from a community builder or evangelist. > > But, that's me. > > *shrug* > > :) > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 16, 2020

Re: [Pharo-users] ByteArray for UDP datagram

by Sven Van Caekenberghe

> On 16 Jan 2020, at 12:11, HilaireFernandes <hilaire(a)drgeo.eu> wrote: > > Thanks Sven, it works. > > If understood correctly ByteArray on streaming only accept ByteArray. > I wonder, should the string be terminated by a null byte, as exepcted on C? That dependents on your protocol's definition/spec. It is easy to add a null byte, stream nextPut: 0 In some protocols, strings are encoded with a byte length prefix. > Hilaire > > > > ----- > http://drgeo.eu > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Jan. 16, 2020

Re: [Pharo-users] Pharo Quality Rules for Beginners

by Kasper Ãsterbye

On 16 January 2020 at 14.20.03, Ben Coman (btc(a)openinworld.com) wrote: An error message like "Blah doesn't understand self" is a bit complex for a beginner to decipher. I would like to second this one! If you want to have *beginners mode*, I think you need to include run-time aspects as well as Ben mentions. It should be possible to put the general doesNotUnderstand in a beginners mode, which checks for these cases - messages send to nil, explaining what is the likely cause(s). - the case mentioned by Ben - check if the message is understood by the class or object (several have mentioned the class/object side issue). - check which classes implements the method which was sent, and perhaps even suggest to open the implementers browser Good luck with the project! Best, Kasper

Jan. 16, 2020

Re: [Pharo-users] Pharo Quality Rules for Beginners

by Ben Coman

On Wed, 15 Jan 2020 at 17:41, ESTEBAN VILLALOBOS DIAZ via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello everyone! > > My name is Esteban and I will be working on the Pharo Quality Rules for the next few months. The goal is to create different profiles for the rules according to the programming experience of the user. For example, for the beginner profile we would like to check for common mistakes made by people who are just starting with Pharo like: > > Sending self as a message (probably because they forgot a . ) > Using False instead of false > etc.. > > I would appreciate it if you could share with me other common mistakes that you have seen beginners do, or maybe tell me a bit of your own experience when you started using Pharo :) - Getting confused between instance-side and class-side, mixing up which side methods are on. When getting a DNU maybe check if that message is known on the class-side. - leaving out the end of statement trailing dot. An error message like "Blah doesn't understand self" is a bit complex for a beginner to decipher. cheers -ben

Jan. 16, 2020

Re: [Pharo-users] ByteArray for UDP datagram

by HilaireFernandes

Thanks Sven, it works. If understood correctly ByteArray on streaming only accept ByteArray. I wonder, should the string be terminated by a null byte, as exepcted on C? Hilaire ----- http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 16, 2020

Re: [Pharo-users] Pharo Quality Rules for Beginners

by pmissech

Hello, First, good luck ! That seems quite interesting ! Few things i can think of: - message priority is often hard to understand, although I'm not sure how that could transform into a rule. - I didn't see this one that often, but since we loose arithmetic priority for message one, I'm pretty sure that could bother some. - miss use of the difference between 'SubclassResponsability' and 'self subclassResponsibility' (and other of this kind i guess, such as shouldNotImplement (I actually just found a very old one in my code :') ) Pierre On 15/01/2020 10:41, ESTEBAN VILLALOBOS DIAZ via Pharo-users wrote:

Jan. 16, 2020

Re: [Pharo-users] Smalltalk: Itâs Not Your Grandfatherâs Programming Language

by HilaireFernandes

If correctly understood your article, Pharo is for programming language, what Tesla is for car. Or more shortly Pharo is the Tesla of programming language? ----- http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 16, 2020

Re: [Pharo-users] ByteArray for UDP datagram

by Sven Van Caekenberghe

Hilaire, You should use a character encoder, for example like this: | packet | packet := ByteArray streamContents: [:str | str nextPut: 16r02; "TOSERVER_INIT" nextPut: 28; "SER_FMT_VER_HIGHEST_READ" uint16: 0; "NETPROTO_COMPRESSION_NONE" uint16: 37; "CLIENT_PROTOCOL_VERSION_MIN" uint16: 38; "LATEST_PROTOCOL_VERSION" nextPutAll: ('Player' encodeWith: #utf8). "Player name" ]. packet contents. Note that there are different options: 'Player' encodeWith: #utf8. 'Player' encodeWith: #null. 'Player' encodeWith: #ascii. But for an ASCII string they give the same result. #null asZnCharacterEncoder. #ascii asZnCharacterEncoder. There is also #utf8Encoded on String. Sven > On 16 Jan 2020, at 11:54, HilaireFernandes <hilaire(a)drgeo.eu> wrote: > > | packet | > packet := ByteArray streamContents: [:str | > str nextPut: 16r02; "TOSERVER_INIT" > nextPut: 28; "SER_FMT_VER_HIGHEST_READ" > uint16: 0; "NETPROTO_COMPRESSION_NONE" > uint16: 37; "CLIENT_PROTOCOL_VERSION_MIN" > uint16: 38; "LATEST_PROTOCOL_VERSION" > nextPutAll: 'Player'. "Player name" > ]. > packet contents

Jan. 16, 2020

ByteArray for UDP datagram

by HilaireFernandes

Hello, I want to fill a byte array, but this code does not work: | packet | packet := ByteArray streamContents: [:str | str nextPut: 16r02; "TOSERVER_INIT" nextPut: 28; "SER_FMT_VER_HIGHEST_READ" uint16: 0; "NETPROTO_COMPRESSION_NONE" uint16: 37; "CLIENT_PROTOCOL_VERSION_MIN" uint16: 38; "LATEST_PROTOCOL_VERSION" nextPutAll: 'Player'. "Player name" ]. packet contents nor this variant: | packet | packet := OrderedCollection streamContents: [:str | str nextPut: 16r02; "TOSERVER_INIT" nextPut: 28; "SER_FMT_VER_HIGHEST_READ" uint16: 0; "NETPROTO_COMPRESSION_NONE" uint16: 37; "CLIENT_PROTOCOL_VERSION_MIN" uint16: 38; "LATEST_PROTOCOL_VERSION" nextPutAll: 'Player'. "Player name" ]. (ByteArray withAll: packet contents) inspect Given the packet must to be filled with byte, short, double, string, what is the best/neat way to prepare packet for datagram? Thanks Hilaire ----- http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 16, 2020