On Fri, Mar 08, 2013 at 11:23:27AM +0100, stephane ducasse wrote: > > On Mar 8, 2013, at 2:52 AM, David T. Lewis <[email protected]> wrote: > > > On Thu, Mar 07, 2013 at 11:23:22PM +0100, Sven Van Caekenberghe wrote: > >> Hi Eliot, > >> > >> On 07 Mar 2013, at 23:12, Eliot Miranda <[email protected]> wrote: > >> > >>> I seem to be talking to thin air. If you would use an up-to-date VM your > >>> crashes would disappear. This bug was fixed this last week. You are > >>> using a VM from December of last year. Of course if you don't want to > >>> fix your bug lease continue to ignore anything I might have to say. > >> > >> I tried using your latest cog vm, but the Pharo 2.0 image side check > >> complained: > >> > >> checkVMVersion > >> "Display a warning if the VM is too old" > >> | displayError | > >> displayError := [ ^ self inform: 'Your VM is too old for this image. > >> Please download the latest VM.' ]. > >> [(VirtualMachine interpreterSourceDate > '2012-07-08+2:00' asDate) > >> ifFalse: displayError > >> ] on: Error do: [ :e| displayError value ]. > >> > >> I was unsure if this was a real problem or not ? > > > > This method in the image is completely wrong and misleading. The VM that > > was being used is clearly *not* out of date. If the intent is to give the > > user a message that says "please use only the latest Pharo VM", then it > > should > > say so. > > I do not understand why. I want to know that I'm not using a VM supporting > fileplugin latest addition.
I was trying to suggest a more meaningful message for the use case of a user running Pharo on a non-Pharo VM. The message says to get a newer VM, which is wrong in that case. Yes I understand that I am not part of the target market. I am a person who is trying to maintain external packages for Squeak and Pharo. Sometimes I need to use another VM in order to do that, so I think it's a legitimate use case. Dave > > > To check explicitly for a Pharo VM I would suggest adding a primitive or VM > > parameter that identifies the VM as Pharo-specific so the checkVMVersion can > > distinguish an out-of-date Pharo VM and provide an appropriate warning > > message. > > > > It is really not fair to ask Eliot to spend his time debugging "Cog > > problems" > > when the image is sending incorrect error messages. > > > > Dave > > > > >
