- Pharo-dev - lists.pharo.org

A better way to serialise methods?
by Aliaksei Syrel June 28, 2017

June 28, 2017

Hi, Smalltalk is famous for tiny methods with just a few parameters. However, sometimes libraries written in C have methods that accept many arguments. In my case I have a method that requires to pass exactly 15 arguments, luckily 15 is maximum possible amount of arguments in Pharo, so my day was saved. Until I tried to load the same code in Window. Here is my ffi call method: primMeasure: aTextRun start: aStart length: aMaxLength breakBefore: aLineBreakBefore width: aWidth provider: aProvider suppress: aSuppressBreak whitespace: aTrimWhitespace metrics: aMetrics boxType: aBoundingBoxType canvas: aCanvas hyphen: aUsedHyphenation lastBreak: aLastBreak wordWrap: aCanWordWrap breakPriority: aBreakPriorityPointer ^ self ffiCall: #(uint32 text_run_break_and_measure ( TextRun aTextRun, uint32 aStart, uint32 aMaxLength, bool aLineBreakBefore, double aWidth, TextPropertyProvider aProvider, TextSuppressBreak aSuppressBreak, ExternalAddress aTrimWhitespace, NativeTextMetrics aMetrics, TextBoundingBoxType aBoundingBoxType, Canvas aCanvas, ExternalAddress aUsedHyphenation, ExternalAddress aLastBreak, bool aCanWordWrap, ExternalAddress aBreakPriorityPointer)) If I try to commit it using filetree/gitfiletree/Iceberg I get an .st method source file with the following name (138 characters): > > primMeasure.start.length.breakBefore.width.provider.suppress.whitespace.metrics.boxType.canvas.hyphen.lastBreak.wordWrap.breakPriority..st And of course trying to clone the repo using git fails on Window because filename is too long. So here comes the question: *Is it really necessary to name method source file according to the method's #sender? Would it make sense to trim the filename and append a short hash to avoid collisions?* Cheers, Alex

2 1

debug vm windows?
by Andrei Chis June 28, 2017

June 28, 2017

Hi, Is there a Pharo debug vm for windows already build and available somewhere? Cheers, Andrei

3 5

Working OSProcess configuration for Pharo 6 release (please)
by ClÃ©ment Bera June 28, 2017

June 28, 2017

Hi Thierry, hi all, The Pharo catalog version of OSProcess is not working in the Pharo 6 release and I need to load OSProcess in one of my projects. I cannot load OSSubProcess instead, so no need to answer this mail talking about it. In-between version 2231 and 2241 of VMMaker, the vm parameter 1002 (os version), has changed on Mac from '1011.6' to '10.11.6'. OSProcess tests the version number against 1000, and should now test against 10. I checked the SqueakSource repo of OSProcess, I can see that the last version is 4.6.8 and the catalog configuration loads an older version, but I cannot see any fix related to the version number ? Can someone update the OSProcess configuration in the Pharo catalog so that it loads a working version in the Pharo 6 release or point me to an OSProcess configuration, outside of the catalog, which works in the release of Pharo 6 please ? Thank you very much. Clement

7 14

[pharo-project/pharo-core]
by GitHub June 28, 2017

June 28, 2017

Branch: refs/tags/60503 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 72b8b1: 60503
by GitHub June 28, 2017

June 28, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 72b8b154b3e120d81e3bf1cb7212a4202892cc85 https://github.com/pharo-project/pharo-core/commit/72b8b154b3e120d81e3bf1cb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-06-28 (Wed, 28 Jun 2017) Changed paths: M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F26%5F8_.st M FFI-Pools.package/FFIConstants.class/README.md M FFI-Pools.package/FFIConstants.class/class/pool initialization/initialize.st A FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeCallingConventions.st A FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeErrorConstants.st A FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeTypeConstants.st R FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeCallingConventions.st R FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeErrorConstants.st R FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeTypeConstants.st M Graphics-Files.package/PNGReadWriter.class/instance/pixel copies/copyPixelsRGBA_.st M Graphics-Files.package/PNGReadWriter.class/instance/pixel copies/copyPixelsRGBA_at_by_.st M Graphics-Files.package/PNGReadWriter.class/instance/pixel copies/copyPixelsRGB_.st M Graphics-Files.package/PNGReadWriter.class/instance/pixel copies/copyPixelsRGB_at_by_.st A Graphics-Tests.package/PNGReadWriterTest.class/instance/tests - decoding/testNewFromSampleBytes.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60502.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60503.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60502.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60503.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI.package/FFICallbackType.class/instance/emitting code/offsetWriteFieldAt_with_.st M UnifiedFFI.package/FFIExternalStructure.class/class/accessing/structureAlignment.st A UnifiedFFI.package/FFIExternalStructureReferenceHandle.class/instance/accessing/getHandle.st M UnifiedFFI.package/FFIExternalStructureType.class/instance/emitting code/offsetReadReferenceAt_.st M UnifiedFFI.package/FFIExternalStructureType.class/instance/emitting code/readReferenceAt_.st M UnifiedFFI.package/FFISizeT.class/class/converting/asExternalTypeOn_.st A UnifiedFFI.package/FFISizeT.class/instance/emitting code/readFieldAt_.st A UnifiedFFI.package/FFISizeT.class/instance/emitting code/writeFieldAt_with_.st M UnifiedFFI.package/FFISizeT.class/instance/private/basicHandle_at_.st M UnifiedFFI.package/FFISizeT.class/instance/private/basicHandle_at_put_.st M UnifiedFFI.package/extension/ExternalType/instance/offsetReadFieldAt_.st A UnifiedFFI.package/extension/ExternalType/instance/offsetReadStructFieldAt_.st M UnifiedFFI.package/extension/ExternalType/instance/offsetWriteFieldAt_with_.st A UnifiedFFI.package/extension/ExternalType/instance/offsetWriteStructFieldAt_with_.st Log Message: ----------- 60503 20167 Regression with PNGReaderWriter in P6 https://pharo.fogbugz.com/f/cases/20167 20198 inner structure access does not work on multiple architecture https://pharo.fogbugz.com/f/cases/20198 http://files.pharo.org/image/60/60503.zip

1 0

Why is there a __MACOSX directory in the zeroconf linux download?
by Tim Mackinnon June 28, 2017

June 28, 2017

Hi - I just noticed when trying out zeroconf on an EC2 instance that the resulting download for the 64 bit vm has a __MACOSX directory in it in the pharo-vm/lib/5.x directory? Isnât this built with a CI server - so why is that file in there? Or are these vmâs hand built? Tim

1 0

GSoC 2017 - Week 7 Update - Enhancing Pharo Command Line Interface
by Rajula Vineet June 28, 2017

June 28, 2017

Hi all, Sorry I couldn`t post updates for a few weeks. Recently, I started working on implementing clap-st as a command line handler in Pharo. During the last few weeks I have worked on the new working directory implementation. For the last week blog post, I wrote a post on SessionManagers <https://vineetreddy.wordpress.com/2017/06/28/session-manager-in-pharo/> . It would be helpful if you can give your feedback on this. Thanks in advance. Rajula -- View this message in context: http://forum.world.st/GSoC-2017-Week-7-Update-Enhancing-Pharo-Command-Line-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Windows 10 crash - LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.
by Andrei Chis June 27, 2017

June 27, 2017

Hi, On Windows 10 with the Pharo 6 release and the latest vm [1] I get the following crash when attempting to save the image after doing some more intensive computations: ------------------------------------------------------------------------------------------ # Debug console # To close: F2 -> 'debug options' -> 'show output console' # To disable: F2 -> 'debug options' -> 'show console on errors' LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) ------------------------------------------------------------------------------------------ The image take around 600MB before the crash but that is expected. I've seen that this error was appearing before in the past. Any suggestions of how to debug it? Cheers, Andrei [1] http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201706211817-f544…

3 2

zero size pharo vm zips
by Nicolai Hess June 27, 2017

June 27, 2017

http://files.pharo.org/vm/pharo-spur32/win/ All vm-zips from the last days have size 0

2 1

Flattened traits in Pharo 7
by Pavel Krivanek June 27, 2017

June 27, 2017

Hi, because we want to have traits only as an option where people will be able to choose custom traits implementation, the Pharo kernel cannot depend on them. For that reason we had to flatten all classes that use traits in the kernel packages. That means that methods from system traits as TBehavior [1] were copied to the trait users and the traits were removed from the class definitions. For now these traits are still present in the image. If you use own traits in your projects, this step will have no impact on you. Only if your project extends the system traits, you will need to adopt it for Pharo 7. [1] complete list: TApplyingOnClassSide TBehavior TBehaviorCategorization TClass TClassDescription TComposingDescription TSortable TTranscript TTransformationCompatibility Cheers, -- Pavel

4 7