- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SmallLint

by Hernan Wilkinson

yes you are right, I remember now, but I think it did not provide more than smalllint does... Also the links to its site are broken 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com> > A bit OT, but there is also another SmallLint called SwaLint. I didn't > remember if it works on pharo, but perhaps you can give it a try. Here a > thread about its ann: > > http://www.nabble.com/-squeak-dev---ANN--SwaLint-tc17403364.html#a17403364 > > Best, > > Mariano > > > On Tue, May 19, 2009 at 12:35 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> http://code.google.com/p/pharo/wiki/SmallLintPharoFixing >> >> >> On May 19, 2009, at 1:55 PM, Hernan Wilkinson wrote: >> >> > Hi, >> > some years ago I ported a tool we created in VisualAge called >> > ExpectedSmallLintFailures to Squeak ( >> http://map.squeak.org/package/25c17dc0-bf31-4215-8ba9-bf0df8157449 >> > ) >> > That tool allows to register expected smalllint failures to avoid >> > getting false positives everytime you run smalllint. I tried to load >> > it yesterday in pharo and I had some problems because SmallLint's >> > design has changed a lot (I like it much better the way it is now). >> > I could loaded it finally, but it does not run. >> > So, is there a way to register false positives in the "new small >> > lint"? >> > I'd like to know also if there is a way to run just the bugs or a >> > specific rule (and not all the smalllint rules) using the code >> > critics UI. >> > >> > Thanks! >> > Hernan. >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

Re: [Pharo-project] SmallLint

by Hernan Wilkinson

cool!I tried and it worked for the "long method" rule (as in the example), but I could not make it work for "Message sent not implemented", do you know why? Maybe I have to put the message not implemented in the pragma? how? Also, how do you specify a false positive on a class, not on methods? (for example "Class not referenced") And for variables? (for example "Variables not referenced") Thanks! Hernan. On Tue, May 19, 2009 at 10:35 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > http://code.google.com/p/pharo/wiki/SmallLintPharoFixing > > > On May 19, 2009, at 1:55 PM, Hernan Wilkinson wrote: > > > Hi, > > some years ago I ported a tool we created in VisualAge called > > ExpectedSmallLintFailures to Squeak ( > http://map.squeak.org/package/25c17dc0-bf31-4215-8ba9-bf0df8157449 > > ) > > That tool allows to register expected smalllint failures to avoid > > getting false positives everytime you run smalllint. I tried to load > > it yesterday in pharo and I had some problems because SmallLint's > > design has changed a lot (I like it much better the way it is now). > > I could loaded it finally, but it does not run. > > So, is there a way to register false positives in the "new small > > lint"? > > I'd like to know also if there is a way to run just the bugs or a > > specific rule (and not all the smalllint rules) using the code > > critics UI. > > > > Thanks! > > Hernan. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

Re: [Pharo-project] SmallLint

by Mariano Martinez Peck

A bit OT, but there is also another SmallLint called SwaLint. I didn't remember if it works on pharo, but perhaps you can give it a try. Here a thread about its ann: http://www.nabble.com/-squeak-dev---ANN--SwaLint-tc17403364.html#a17403364 Best, Mariano On Tue, May 19, 2009 at 12:35 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > http://code.google.com/p/pharo/wiki/SmallLintPharoFixing > > > On May 19, 2009, at 1:55 PM, Hernan Wilkinson wrote: > > > Hi, > > some years ago I ported a tool we created in VisualAge called > > ExpectedSmallLintFailures to Squeak ( > http://map.squeak.org/package/25c17dc0-bf31-4215-8ba9-bf0df8157449 > > ) > > That tool allows to register expected smalllint failures to avoid > > getting false positives everytime you run smalllint. I tried to load > > it yesterday in pharo and I had some problems because SmallLint's > > design has changed a lot (I like it much better the way it is now). > > I could loaded it finally, but it does not run. > > So, is there a way to register false positives in the "new small > > lint"? > > I'd like to know also if there is a way to run just the bugs or a > > specific rule (and not all the smalllint rules) using the code > > critics UI. > > > > Thanks! > > Hernan. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

[Pharo-project] Win32Setup - custom VM and app tutorial

by Torsten Bergmann

>Better hope noone installs to C:\! Hey - be a man and try it! No fear - the installer button is disabled then (already catched by NSIS). >it's probably a good idea to specify the files to delete specifically OK - would be a good style, I've updated the NSIS script. Since we now also have nice icons here more additions to the former tutorial: - a welcome.bmp on the left is shown - a header.bmp is shown on top - the icon for the install and VM is much better (incl. transparency and different icon sizes up to 256x256 for Vista, ...) - the setup allows to run pharo after installation Attached are the files necessary, just copy them to the "pharodist" directory and run the NSIS script. A new pharo Windows setup (setup_pharo_0.0.0.2.exe) is now available on http://gforge.inria.fr/frs/download.php/22311/setup_pharo_0.0.0.2.exe Thanks to all for making this possible - with the pharo distribution Squeak now really has stopped looking toyish. Only 10MB download for a complete world full of Smalltalk :) Have fun Torsten -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 19, 2009

Re: [Pharo-project] vw inspired gui tool

by Steve Wirts

Stephane, I've done another go round with this, let me know if this is closer to what you are thinking. Thanks Steve On Fri, May 15, 2009 at 4:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes this would be great. > I think that this is important to get better tools not more tools :) > > Stef > > On May 15, 2009, at 10:17 PM, Steve Wirts wrote: > > > Stef, > > > > Only submorphs, the gui hierarchy are shown, this is a really useful > > capability when trying to understand deeply nested complex gui > > structures. I suppose we could put a toggle button on a menu option > > on explorer to turn on differernt tree-paths to show as the sub- > > children. > > > > I will try to do that. > > > > thanks > > steve > > > > > > On Fri, May 15, 2009 at 3:33 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr > > > wrote: > > Hi steve > > > > what is the difference with the explorer. > > If you want to have flash just send us a new menu for explorer? > > > > Stef > > > > On May 15, 2009, at 8:46 PM, Steve Wirts wrote: > > > > > Folks, > > > > > > Attached is a very simple gui tool inspired from a tool that used to > > > exist in VW smalltalk years ago. > > > I suspect it could be rewritten as a single function. Please > > > incorporate into Pharo if you think > > > it's useful. > > > > > > Steve > > > <ViewExplorer.st>_______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

Re: [Pharo-project] SmallLint

by StÃ©phane Ducasse

http://code.google.com/p/pharo/wiki/SmallLintPharoFixing On May 19, 2009, at 1:55 PM, Hernan Wilkinson wrote: > Hi, > some years ago I ported a tool we created in VisualAge called > ExpectedSmallLintFailures to Squeak (http://map.squeak.org/package/25c17dc0-bf31-4215-8ba9-bf0df8157449 > ) > That tool allows to register expected smalllint failures to avoid > getting false positives everytime you run smalllint. I tried to load > it yesterday in pharo and I had some problems because SmallLint's > design has changed a lot (I like it much better the way it is now). > I could loaded it finally, but it does not run. > So, is there a way to register false positives in the "new small > lint"? > I'd like to know also if there is a way to run just the bugs or a > specific rule (and not all the smalllint rules) using the code > critics UI. > > Thanks! > Hernan. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2009

Re: [Pharo-project] Regarding Alien: IA32ABI plugin

by StÃ©phane Ducasse

thanks fernando this is important that we get to know what is happening there :) Stef On May 19, 2009, at 2:41 AM, Fernando olivero wrote: > Hello John, > > I need to modify IA32ABI plugin, (the ALIEN plugin), because the > specialObjectsArray was modified and its size is now 50 instead of 52, > as the plugin assumes. > > So both methods Alien>>ensureInSpecialObjectsArray and > UnsafeAlien>>ensureInSpecialObjectsArray can have the proper index of > 51 and 53, instead of the previous 53 and 55. > > Could you tell me in what part of the plugin i should modify it? so i > can build a new one. > > > Thanks! > Fernando > > pd: i'm forwarding this to the list in case anyone else can help! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Mariano Martinez Peck

On Tue, May 19, 2009 at 6:46 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > To me, this raises a more general question. > How can we trace a particular change in Pharo? > Why when and where this change did occur? I know all is in the > Monticello repository, but is there a quick and convenient way to > answer such a question? I mean avoiding a manual scan of each and > every Monticello version... > > Or is it logged in the ChangeSet? In this case, what hidden menu or > code snippet will help tracking the change? > > Or should we use the issue tracker? Ideally, the reason for every > change should be logged here. And every Monticello uploaded should > refer to an issue. Even if this were strictly applied, not sure that > is the way to retrieve information at such a detailed level. > > If none of these tools can provide an easy answer, then yes, requests > on mailing lists, IRC, or internet search can provide a much efficient > answer. But that's the signature a tool is lacking. > I am agree. Actually, I thought to add in my email a generic question of that because I faced this problem several times and I didn't know what to do. > I wish Mariano gets an answer, but an answer on the method would be > more profitable to every one. No problem. Perhaps someone knows haha. > > > Cheers > > Nicolas > > 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi folks. I noticed that this two methods were removed from > > ThirtyTwoBitRegister: > > > > asByteArray > > ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: -8) > with: > > (hi bitAnd: 16rFF) with: (hi bitShift: -8) > > > > > > > > reverseLoadFrom: aByteArray at: index > > "Load my 32-bit value from the four bytes of the given > > ByteArraystarting at the given index. Consider the first byte to contain > the > > mostsignificant bits of the word (i.e., use big-endian byte ordering)." > > > > hi := ((aByteArray at: index + 3) bitShift: 8) + ( aByteArray > at: > > index + 2). > > low := ((aByteArray at: index + 1) bitShift: 8) + ( aByteArray > at: > > index). > > > > > > > > I need them for Glorp. I looked but I didn't found a similar message for > > them. I don't think adding them as an extension is a good solution here > > since this seems to be very "internal". is there a reason of the > removing? > > If not, could them be added again? If there are reason, which should be > the > > best approach to fix this in mi case? > > > > I have no problem in commit them if you want. > > > > Thanks! > > > > Mariano > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

Re: [Pharo-project] Win32Setup - custom VM and app tutorial

by Henrik Johansen

Better hope noone installs to C:\! :) (i.e. it's probably a good idea to specify the files to delete specifically ) Cheers, Henry Torsten Bergmann skrev: > Section "Uninstall" > > SetOutPath $INSTDIR > DetailPrint "Start uninstalling" > Delete "$INSTDIR\*.*" > > ;delete uninstaller > Delete "$INSTDIR\Uninstall.exe" > RmDir /r /REBOOTOK "$SMPROGRAMS\${MGROUP}" > RmDir /REBOOTOK $INSTDIR > DeleteRegKey /ifempty HKCU "${REG_KEY}" > SectionEnd > >

May 19, 2009

[Pharo-project] SmallLint

by Hernan Wilkinson

Hi, some years ago I ported a tool we created in VisualAge called ExpectedSmallLintFailures to Squeak ( http://map.squeak.org/package/25c17dc0-bf31-4215-8ba9-bf0df8157449) That tool allows to register expected smalllint failures to avoid getting false positives everytime you run smalllint. I tried to load it yesterday in pharo and I had some problems because SmallLint's design has changed a lot (I like it much better the way it is now). I could loaded it finally, but it does not run. So, is there a way to register false positives in the "new small lint"? I'd like to know also if there is a way to run just the bugs or a specific rule (and not all the smalllint rules) using the code critics UI. Thanks! Hernan.

May 19, 2009