A challenge for all who cares
Locked
12
12
A challenge for all who cares
 
|
That’s is a beauty and the power of Cuis, thanks Juan for your reduced image of 2 mb 117.192.108.122 178.64.152.244 190.18.66.65 190.193.183.54 190.216.29.120 190.99.158.210 201.212.74.182 201.252.254.21 64.151.43.167 76.110.216.6 76.15.23.5 76.68.49.175 86.42.80.90 88.161.169.54 92.225.135.195 93.38.215.238 This was the captured Ip, ranging from Atlanta, Paris,Milano, St Petersbourg, Hamburg, Sunchales, Buenos Aires . Off course some have halts as all is towards to alpha real soon now :=) In the process I fix some errors of the wiki, discover Cuis do not know how import Morph and must to do a mix between Juan code which is superior and old Squeak code just for compatibility. Lo lamento Juan por ensuciar el Cuis. So the challenge is: Taking http://ftp.squeak.org/various_images/SqueakLight/Cuis3.1r.4.zip as target we could build it from Spoon ? And add the best of Pharo, Squeak, whatever (external JavaScript) for having a killer system which document to self like Cuis3.1r.11.image running today on http://201.212.74.182:8086/ Siganme los buenos ! Edgar P.S Fell free to contact direct to [hidden email] Edgar |
Re: A challenge for all who cares
|
|
Sounds cool editing and executing Smalltalk code in a Wiki! :-) Have fun! Guido Stepken Am 20.02.2012 11:21 schrieb "Edgar J. De Cleene" <[hidden email]>:
|
Re: A challenge for all who cares
|
|
In reply to this post by Edgar De Cleene
Am 20.02.2012 10:22, schrieb Edgar J. De Cleene:
Looks nice. World menu -> appearance -> set desktop color -> Error What i - never ever - understand is, why - when Smalltalk is a reflective language and there are so mighty tools - like Moose - out there, able to search the whole codebase for possible occurrences of "message not understood"????? This is no personal quality problem, this is a methodical problem. In the whole Pharo team. "Wrong development process!" Please, again: "Develop the development process!" Have fun, Guido Stepken |
Re: A challenge for all who cares
|
|
On 20 February 2012 20:41, Guido Stepken <[hidden email]> wrote:
> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: > > Yesterday in a response to Craig I said have a Cuis with a wiki on top and > this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. > > That’s is a beauty and the power of Cuis, thanks Juan for your reduced image > of 2 mb > > > Looks nice. > > World menu -> appearance -> set desktop color -> Error > > What i - never ever - understand is, why - when Smalltalk is a reflective > language and there are so mighty tools - like Moose - out there, able to > search the whole codebase for possible occurrences of "message not > understood"????? If you would learn smalltalk, you would understand that there's no such tool. It could search, and even may found some, but still it impossible to find all. This is the main difference between late-bound dynamic language and static, compiled one. To deal with stupid errors like that, smalltalk uses tests with good code coverage. But that means that someone has to write them. > > This is no personal quality problem, this is a methodical problem. In the > whole Pharo team. "Wrong development process!" > Yes, we know. DRY. If there's no test, it won't magically appear even if you have right development process, unless someone will write it. Flaming on mailing list doesn't helps either way. > Please, again: "Develop the development process!" > > Have fun, Guido Stepken -- Best regards, Igor Stasenko. |
Re: A challenge for all who cares
|
|
In reply to this post by Guido Stepken
On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote:
> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: > > Yesterday in a response to Craig I said have a Cuis with a wiki on top and > this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. > > That’s is a beauty and the power of Cuis, thanks Juan for your reduced image > of 2 mb > > > Looks nice. > > World menu -> appearance -> set desktop color -> Error > > What i - never ever - understand is, why - when Smalltalk is a reflective > language and there are so mighty tools - like Moose - out there, able to > search the whole codebase for possible occurrences of "message not > understood"????? This is just a trivial application of the solution to the Halting Problem (left as an exercise for the reader). Or: if you want to avoid MNU, don't use a dynamically typed language. frank > This is no personal quality problem, this is a methodical problem. In the > whole Pharo team. "Wrong development process!" > > Please, again: "Develop the development process!" > > Have fun, Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Igor Stasenko
On 20 February 2012 19:59, Igor Stasenko <[hidden email]> wrote:
> On 20 February 2012 20:41, Guido Stepken <[hidden email]> wrote: >> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >> >> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >> >> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >> of 2 mb >> >> >> Looks nice. >> >> World menu -> appearance -> set desktop color -> Error >> >> What i - never ever - understand is, why - when Smalltalk is a reflective >> language and there are so mighty tools - like Moose - out there, able to >> search the whole codebase for possible occurrences of "message not >> understood"????? > > If you would learn smalltalk, you would understand that there's no such tool. > It could search, and even may found some, but still it impossible to find all. > This is the main difference between late-bound dynamic language and > static, compiled one. > > To deal with stupid errors like that, smalltalk uses tests with good > code coverage. > But that means that someone has to write them. Even 100% code coverage - and I mean per branch, not per method - is insufficient to prevent an MNU. Even if your code is perfect, someone can throw something random into your neat library, and hey presto! And we all know this, and choose the possibility of MNUs because dynamic typing meets our needs. frank >> This is no personal quality problem, this is a methodical problem. In the >> whole Pharo team. "Wrong development process!" >> > Yes, we know. DRY. > If there's no test, it won't magically appear even if you have right > development process, unless someone will write it. Flaming on mailing > list doesn't helps either way. > >> Please, again: "Develop the development process!" >> >> Have fun, Guido Stepken > > > > -- > Best regards, > Igor Stasenko. > |
Re: A challenge for all who cares
|
|
In reply to this post by Frank Shearar-3
On 20 February 2012 21:18, Frank Shearar <[hidden email]> wrote:
> On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote: >> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >> >> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >> >> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >> of 2 mb >> >> >> Looks nice. >> >> World menu -> appearance -> set desktop color -> Error >> >> What i - never ever - understand is, why - when Smalltalk is a reflective >> language and there are so mighty tools - like Moose - out there, able to >> search the whole codebase for possible occurrences of "message not >> understood"????? > > This is just a trivial application of the solution to the Halting > Problem (left as an exercise for the reader). > Apparently compilers can complain about using wrong type/name.. but they cannot complain about null pointer(s).. they usually crash & bail to OS :) > Or: if you want to avoid MNU, don't use a dynamically typed language. > > frank > >> This is no personal quality problem, this is a methodical problem. In the >> whole Pharo team. "Wrong development process!" >> >> Please, again: "Develop the development process!" >> >> Have fun, Guido Stepken > -- Best regards, Igor Stasenko. |
Re: A challenge for all who cares
|
|
In reply to this post by Frank Shearar-3
Le 20 février 2012 21:18, Frank Shearar <[hidden email]> a écrit :
> On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote: >> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >> >> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >> >> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >> of 2 mb >> >> >> Looks nice. >> >> World menu -> appearance -> set desktop color -> Error >> >> What i - never ever - understand is, why - when Smalltalk is a reflective >> language and there are so mighty tools - like Moose - out there, able to >> search the whole codebase for possible occurrences of "message not >> understood"????? > > This is just a trivial application of the solution to the Halting > Problem (left as an exercise for the reader). > > Or: if you want to avoid MNU, don't use a dynamically typed language. > What, what, the right development process wouldn't solve such a trivial problem ? Guido, try to inspect yourself with all your introspection tools and development process know how, because I have the feeling that despite the many answers you got, you still face a message not understood problem ;) Nicolas > frank > >> This is no personal quality problem, this is a methodical problem. In the >> whole Pharo team. "Wrong development process!" >> >> Please, again: "Develop the development process!" >> >> Have fun, Guido Stepken > |
Re: A challenge for all who cares
|
|
Am 20.02.2012 um 21:30 schrieb Nicolas Cellier <[hidden email]>: > Le 20 février 2012 21:18, Frank Shearar <[hidden email]> a écrit : >> On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote: >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> >> Or: if you want to avoid MNU, don't use a dynamically typed language. >> > > What, what, the right development process wouldn't solve such a > trivial problem ? > Guido, try to inspect yourself with all your introspection tools and > development process know how, because I have the feeling that despite > the many answers you got, you still face a message not understood > problem ;) > ha ha, made my day, thanks, Norbert > Nicolas > >> frank >> >>> This is no personal quality problem, this is a methodical problem. In the >>> whole Pharo team. "Wrong development process!" >>> >>> Please, again: "Develop the development process!" >>> >>> Have fun, Guido Stepken >> > |
Re: A challenge for all who cares
|
|
In reply to this post by Igor Stasenko
On 20 February 2012 20:24, Igor Stasenko <[hidden email]> wrote:
> On 20 February 2012 21:18, Frank Shearar <[hidden email]> wrote: >> On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote: >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> > I wonder, what kind of language solves that problem better than smalltalk does? > Apparently compilers can complain about using wrong type/name.. but they cannot > complain about null pointer(s).. they usually crash & bail to OS :) The sad thing is that null pointer exceptions are perfectly avoidable in statically typed languages. Er, in decent ones at least! You have to actively work to use nulls in Haskell, for instance. If you have something that might or might not be there, you have an option type: Maybe in Haskell, or Option in Scala. It's just a wrapper that tells you "yes, I have a value, and this is it" or "no, I have no value". (I have a Smalltalk implementation up on http://www.squeaksource.com/Nutcracker/ in the Maybe package. You still have the problem in that you can always say Just value: nil, but it's handy for (a) saying "this is optional" and (b) chaining operations together such that a Nothing stops computation from proceeding.) frank >> Or: if you want to avoid MNU, don't use a dynamically typed language. >> > >> frank >> >>> This is no personal quality problem, this is a methodical problem. In the >>> whole Pharo team. "Wrong development process!" >>> >>> Please, again: "Develop the development process!" >>> >>> Have fun, Guido Stepken >> > > > > -- > Best regards, > Igor Stasenko. > |
Re: A challenge for all who cares
|
|
On 20 February 2012 22:07, Frank Shearar <[hidden email]> wrote:
> On 20 February 2012 20:24, Igor Stasenko <[hidden email]> wrote: >> On 20 February 2012 21:18, Frank Shearar <[hidden email]> wrote: >>> On 20 February 2012 19:41, Guido Stepken <[hidden email]> wrote: >>>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>>> >>>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>>> >>>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>>> of 2 mb >>>> >>>> >>>> Looks nice. >>>> >>>> World menu -> appearance -> set desktop color -> Error >>>> >>>> What i - never ever - understand is, why - when Smalltalk is a reflective >>>> language and there are so mighty tools - like Moose - out there, able to >>>> search the whole codebase for possible occurrences of "message not >>>> understood"????? >>> >>> This is just a trivial application of the solution to the Halting >>> Problem (left as an exercise for the reader). >>> >> I wonder, what kind of language solves that problem better than smalltalk does? >> Apparently compilers can complain about using wrong type/name.. but they cannot >> complain about null pointer(s).. they usually crash & bail to OS :) > > The sad thing is that null pointer exceptions are perfectly avoidable > in statically typed languages. Er, in decent ones at least! You have > to actively work to use nulls in Haskell, for instance. If you have > something that might or might not be there, you have an option type: > Maybe in Haskell, or Option in Scala. It's just a wrapper that tells > you "yes, I have a value, and this is it" or "no, I have no value". > Well yes, you add null to be one of the "expected" values, so you basically turn your input dataset S into (S+nil). but i was actually referring to them as unexpected value(s) which is much harder to deal with. But the problem is that for any input dataset for which your code works, there could be another dataset for which it doesn't, named unexpected input :) Because doing data validity checks at every possible entry point (method) of your application might not what you would like to do. DNU is about dealing with unexpected input, i.e. object receives a message which it cannot understand. So, the question is basically the same: how those languages deal with unexpected input? > (I have a Smalltalk implementation up on > http://www.squeaksource.com/Nutcracker/ in the Maybe package. You > still have the problem in that you can always say Just value: nil, but > it's handy for (a) saying "this is optional" and (b) chaining > operations together such that a Nothing stops computation from > proceeding.) > > frank > >>> Or: if you want to avoid MNU, don't use a dynamically typed language. >>> >> >>> frank >>> >>>> This is no personal quality problem, this is a methodical problem. In the >>>> whole Pharo team. "Wrong development process!" >>>> >>>> Please, again: "Develop the development process!" >>>> >>>> Have fun, Guido Stepken >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > -- Best regards, Igor Stasenko. |
Re: A challenge for all who cares
|
|
In reply to this post by Igor Stasenko
Am 20.02.2012 21:24, schrieb Igor Stasenko:
> On 20 February 2012 21:18, Frank Shearar<[hidden email]> wrote: >> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> > I wonder, what kind of language solves that problem better than smalltalk does? > Apparently compilers can complain about using wrong type/name.. but they cannot > complain about null pointer(s).. they usually crash& bail to OS :) Its string>>base64Decoded error ... missing or removed library/class? No, this must not happen! -> Never ever! -> Develop the development process! Have fun, Guido Stepken > >> Or: if you want to avoid MNU, don't use a dynamically typed language. >> >> frank >> >>> This is no personal quality problem, this is a methodical problem. In the >>> whole Pharo team. "Wrong development process!" >>> >>> Please, again: "Develop the development process!" >>> >>> Have fun, Guido Stepken > > |
Re: A challenge for all who cares
|
|
In reply to this post by Frank Shearar-3
Am 20.02.2012 21:18, schrieb Frank Shearar:
> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >> >> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >> >> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >> of 2 mb >> >> >> Looks nice. >> >> World menu -> appearance -> set desktop color -> Error >> >> What i - never ever - understand is, why - when Smalltalk is a reflective >> language and there are so mighty tools - like Moose - out there, able to >> search the whole codebase for possible occurrences of "message not >> understood"????? > This is just a trivial application of the solution to the Halting > Problem (left as an exercise for the reader). > > Or: if you want to avoid MNU, don't use a dynamically typed language. Thank you, indirectly admitting, that there must be such a tool. ;-) Think! Have fun, Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Nicolas Cellier
Am 20.02.2012 21:30, schrieb Nicolas Cellier:
> Le 20 février 2012 21:18, Frank Shearar<[hidden email]> a écrit : >> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> >> Or: if you want to avoid MNU, don't use a dynamically typed language. >> > What, what, the right development process wouldn't solve such a > trivial problem ? > Guido, try to inspect yourself with all your introspection tools and > development process know how, because I have the feeling that despite > the many answers you got, you still face a message not understood > problem ;) > > Nicolas There *is* a possibility to check, if there is some sender sending something, that a receiver cannot understand. NONSENSE! Do it, develop the development process, insure quality in the code!!! Have fun! Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Guido Stepken
On 20 February 2012 22:58, Guido Stepken <[hidden email]> wrote:
> Am 20.02.2012 21:18, schrieb Frank Shearar: > >> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>> >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top >>> and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced >>> image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> >> Or: if you want to avoid MNU, don't use a dynamically typed language. > > > Thank you, indirectly admitting, that there must be such a tool. ;-) > > Think! > > Have fun, Guido Stepken > -- Best regards, Igor Stasenko. |
Re: A challenge for all who cares
|
|
Am 20.02.2012 23:01, schrieb Igor Stasenko:
> On 20 February 2012 22:58, Guido Stepken<[hidden email]> wrote: >> Am 20.02.2012 21:18, schrieb Frank Shearar: >> >>> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>>> >>>> Yesterday in a response to Craig I said have a Cuis with a wiki on top >>>> and >>>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>>> >>>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced >>>> image >>>> of 2 mb >>>> >>>> >>>> Looks nice. >>>> >>>> World menu -> appearance -> set desktop color -> Error >>>> >>>> What i - never ever - understand is, why - when Smalltalk is a reflective >>>> language and there are so mighty tools - like Moose - out there, able to >>>> search the whole codebase for possible occurrences of "message not >>>> understood"????? >>> This is just a trivial application of the solution to the Halting >>> Problem (left as an exercise for the reader). >>> >>> Or: if you want to avoid MNU, don't use a dynamically typed language. >> >> Thank you, indirectly admitting, that there must be such a tool. ;-) >> > yes, it called human brain. Don't argue. Think about, there *must* be a possibility to avoid such errors! Develop the development process! tnx, Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Nicolas Cellier
Am 20.02.2012 21:30, schrieb Nicolas Cellier:
> What, what, the right development process wouldn't solve such a > trivial problem ? > Guido, try to inspect yourself with all your introspection tools and > development process know how, because I have the feeling that despite > the many answers you got, you still face a message not understood > problem ;) > > Nicolas Nicolas, i *know*, there must be a solution! Cannot be, that i klick into a menu and *directly* run into error messages. Think! Develop the development process! Don't argue! tnx, Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Guido Stepken
A true don quixote of modern times
fighting the endless mills of the halting problem again you made my day :D On 2012-02-20, at 23:01, Guido Stepken wrote: > Am 20.02.2012 21:30, schrieb Nicolas Cellier: >> Le 20 février 2012 21:18, Frank Shearar<[hidden email]> a écrit : >>> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>>> >>>> Yesterday in a response to Craig I said have a Cuis with a wiki on top and >>>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>>> >>>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced image >>>> of 2 mb >>>> >>>> >>>> Looks nice. >>>> >>>> World menu -> appearance -> set desktop color -> Error >>>> >>>> What i - never ever - understand is, why - when Smalltalk is a reflective >>>> language and there are so mighty tools - like Moose - out there, able to >>>> search the whole codebase for possible occurrences of "message not >>>> understood"????? >>> This is just a trivial application of the solution to the Halting >>> Problem (left as an exercise for the reader). >>> >>> Or: if you want to avoid MNU, don't use a dynamically typed language. >>> >> What, what, the right development process wouldn't solve such a >> trivial problem ? >> Guido, try to inspect yourself with all your introspection tools and >> development process know how, because I have the feeling that despite >> the many answers you got, you still face a message not understood >> problem ;) >> >> Nicolas > > There *is* a possibility to check, if there is some sender sending something, that a receiver cannot understand. > > NONSENSE! > > Do it, develop the development process, insure quality in the code!!! > > Have fun! > > Guido Stepken > |
|
|
In reply to this post by Guido Stepken
Guido what are you on?
arghh soooo annoying Think! Don't argue! You're annoying! On 21 Feb 2012, at 12:06 AM, Guido Stepken wrote: Am 20.02.2012 21:30, schrieb Nicolas Cellier: > What, what, the right development process wouldn't solve such a > trivial problem ? > Guido, try to inspect yourself with all your introspection tools and > development process know how, because I have the feeling that despite > the many answers you got, you still face a message not understood > problem ;) > > Nicolas Nicolas, i *know*, there must be a solution! Cannot be, that i klick into a menu and *directly* run into error messages. Think! Develop the development process! Don't argue! tnx, Guido Stepken |
Re: A challenge for all who cares
|
|
In reply to this post by Guido Stepken
On 20 February 2012 21:58, Guido Stepken <[hidden email]> wrote:
> Am 20.02.2012 21:18, schrieb Frank Shearar: > >> On 20 February 2012 19:41, Guido Stepken<[hidden email]> wrote: >>> >>> Am 20.02.2012 10:22, schrieb Edgar J. De Cleene: >>> >>> Yesterday in a response to Craig I said have a Cuis with a wiki on top >>> and >>> this .image is 5 mb and run on a “modern” G4 400 mhz PowerMac. >>> >>> That’s is a beauty and the power of Cuis, thanks Juan for your reduced >>> image >>> of 2 mb >>> >>> >>> Looks nice. >>> >>> World menu -> appearance -> set desktop color -> Error >>> >>> What i - never ever - understand is, why - when Smalltalk is a reflective >>> language and there are so mighty tools - like Moose - out there, able to >>> search the whole codebase for possible occurrences of "message not >>> understood"????? >> >> This is just a trivial application of the solution to the Halting >> Problem (left as an exercise for the reader). >> >> Or: if you want to avoid MNU, don't use a dynamically typed language. > > > Thank you, indirectly admitting, that there must be such a tool. ;-) > > Think! Sure. Given a decent statically typed language you can completely avoid the null problem, at least if you leave out input, which is what Igor's hinting at in his reply to me. And as soon as you allow arbitrary input, you're hosed. That is, you run smack into the entscheidungsproblem. So, no, I was quite explicitly saying that there is provably no such tool. If you're finding a bug, then _report it_. Ideally, _produce a replicable series of steps to expose the bug_. You can program, so _write a test for it_. frank |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |