I was stunned and curious. There's plenty of "false ifTrue:" code in Squeak 4.2... Did I miss something too ??? :)  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blogue: endormitoire.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: "jtuchel@objektfabrik.de" <jtuchel@objektfabrik.de> To: pharo-users@lists.pharo.org Sent: Monday, June 24, 2013 4:28:50 PM Subject: Re: [Pharo-users] Pharo 2.0 and ODBC You're joking, right? I mean, if this is a way of helping me understand code by "commenting it", I'd simply say Thanks, but no thanks! If that's the way it's done in Smalltalk, I wonder where I have been the last 17 years. I haven't done this and I can't remember seeing this. And I've read and fixed quite some code in that time. This is probably done in a Smalltalk environment that has no decent version control system, just to avoid losing code you could probably need again. But I doubt anybody using Monticello or more advanced Smalltalk versioning solutions really needs such a dirty workaround. But I cannot prove you wrong. At least that piece of code is functionally equivalent to a comment ;-) So what you're saying is that I shouldn't worry about it. Okay, will do ;-))) Joachim Am 24.06.13 22:13, schrieb Milan Mimica:
On 24 June 2013 12:21, jtuchel <mailto:jtuchel@objektfabrik.de>wrote:
  false ifTrue:       [ self         sqlSetEnvAttr: 200         value: 2  "SQL_ATTR_ODBC_VERSION" ].
  what does this false ifTrue: thing mean here?
That's how you comment code in Smalltalk - becuase it doesn't support nested comments.
-- Milan Mimica http://sparklet.sf.net