- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Sept. 30, 2016

Sept. 30, 2016

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

1 0

[pharo-project/pharo-core] f68ece: 60243
by GitHub Sept. 30, 2016

Sept. 30, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f68ecefb602be715d886dc5050f9309585ca06a4 https://github.com/pharo-project/pharo-core/commit/f68ecefb602be715d886dc50… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-30 (Fri, 30 Sep 2016) Changed paths: A Kernel.package/CompiledBlock.class/instance/accessing/hash.st A Kernel.package/CompiledBlock.class/instance/accessing/penultimateLiteral.st R Kernel.package/CompiledBlock.class/instance/additions/ast.st R Kernel.package/CompiledBlock.class/instance/additions/hash.st R Kernel.package/CompiledBlock.class/instance/additions/isTestMethod.st R Kernel.package/CompiledBlock.class/instance/additions/pcInOuter.st R Kernel.package/CompiledBlock.class/instance/additions/printOn_.st R Kernel.package/CompiledBlock.class/instance/additions/properties.st R Kernel.package/CompiledBlock.class/instance/additions/sameLiteralsAs_.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNode.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNodeForPC_.st R Kernel.package/CompiledBlock.class/instance/additions/sourceNodeInOuter.st A Kernel.package/CompiledBlock.class/instance/comparing/sameLiteralsAs_.st A Kernel.package/CompiledBlock.class/instance/compatibility/properties.st A Kernel.package/CompiledBlock.class/instance/printing/printOn_.st A Kernel.package/CompiledBlock.class/instance/scanning/hasMethodReturn.st A Kernel.package/CompiledBlock.class/instance/scanning/pcInOuter.st A Kernel.package/CompiledBlock.class/instance/testing/isTestMethod.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteralSuchThat_.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteralThorough_.st M Kernel.package/CompiledCode.class/instance/literals/hasLiteral_.st A Kernel.package/CompiledCode.class/instance/literals/innerCompiledBlocksAnySatisfy_.st A Kernel.package/CompiledCode.class/instance/literals/innerCompiledBlocksDo_.st M Kernel.package/CompiledCode.class/instance/scanning/hasInstVarRef.st A Kernel.package/CompiledCode.class/instance/scanning/localHasInstVarRef.st A Kernel.package/CompiledCode.class/instance/scanning/localMessages.st A Kernel.package/CompiledCode.class/instance/scanning/localReadsRef_.st A Kernel.package/CompiledCode.class/instance/scanning/localSendsToSuper.st A Kernel.package/CompiledCode.class/instance/scanning/localWritesRef_.st M Kernel.package/CompiledCode.class/instance/scanning/messages.st M Kernel.package/CompiledCode.class/instance/scanning/readsField_.st M Kernel.package/CompiledCode.class/instance/scanning/readsRef_.st M Kernel.package/CompiledCode.class/instance/scanning/sendsToSuper.st M Kernel.package/CompiledCode.class/instance/scanning/writesField_.st M Kernel.package/CompiledCode.class/instance/scanning/writesRef_.st A Kernel.package/CompiledMethod.class/instance/scanning/readsField_.st A Kernel.package/CompiledMethod.class/instance/scanning/writesField_.st A Kernel.package/FullBlockClosure.class/instance/scanning/abstractBytecodeMessagesDo_.st A Kernel.package/FullBlockClosure.class/instance/scanning/hasMethodReturn.st R Kernel.package/FullBlockClosure.class/instance/testing/hasMethodReturn.st R Kernel.package/LargeInteger.class/instance/mathematical functions/mightBeASquare.st A Kernel.package/LargeInteger.class/instance/testing/mightBeASquare.st A Kernel.package/LargeNegativeInteger.class/instance/testing/mightBeASquare.st A Kernel.package/LargePositiveInteger.class/instance/testing/mightBeASquare.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/ast.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNode.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNodeForPC_.st A OpalCompiler-Core.package/extension/CompiledBlock/instance/sourceNodeInOuter.st A RPackage-Core.package/RPackage.class/instance/class tags/actualClassTags.st A RPackage-Tests.package/RPackageTest.class/instance/tests/testActualClassTags.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60242.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60243.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60242.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60243.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60243 18032 mightBeASquare should be implemented in LargePositiveInteger https://pharo.fogbugz.com/f/cases/18032 19154 Move to RPackage logic to retrieve actual class tags https://pharo.fogbugz.com/f/cases/19154 19100 Senders of with Full closures https://pharo.fogbugz.com/f/cases/19100 http://files.pharo.org/image/60/60243.zip

1 0

CfP: OOPS @ SAC 2017, deadline extended to October 7th, 2016
by Nick Papoylias Sept. 30, 2016

Sept. 30, 2016

========================================================= ***** SUBMISSION DEADLINE EXTENDED: October 7, 2016 ***** ========================================================= ************************************************** OOPS 2017 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS17 ************************************************** Technical Track at the 32nd ACM Symposium on Applied Computing, SAC 2017 http://www.acm.org/conferences/sac/sac2017 April 3 - 7, 2017 Marrakesh, Morocco - Important Dates Submission of regular papers and SRC abstracts October 7, 2016 (final extended deadline) Paper and SRC notifications November 18, 2016 Paper and SRC camera-ready copies December 2, 2016 Author registration December 10, 2016 SAC 2017 April 3 - 7, 2017 - Track Chair Davide Ancona (davide.ancona(a)unige.it) DIBRIS, University of Genova, Italy - SAC 2017 For the past thirty one years, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for applied computer scientists, computer engineers, software engineers, and application developers from around the world. SAC 2017 is sponsored by the ACM Special Interest Group on Applied Computing (SIGAPP) and is hosted by the University of Quebec at Montreal, Canada; University Cadi Ayyad (UCA) of Marrakech, Morocco; National School of Engineering in Rabat (EMI), Rabat, Morocco; and National School of Applied Sciences (ENSA) of Kenitra, Morocco. - Call For Student Research Abstracts Graduate students seeking feedback from the scientific community on their research ideas are invited to submit original abstracts of their research work in areas of experimental computing and application development related to SAC 2017 Tracks. The Student Research Competition (SRC) Program is designed to provide graduate students the opportunity to meet and exchange ideas with researchers and practitioners in their areas of interest. - OOPS Track: Aims and Topics Object-oriented programming (OOP) has become the mainstream programming paradigm for developing complex software systems in most application domains. However, existing OO languages and platforms need to evolve to meet the continuous demand for new abstractions, features, and tools able to reduce the time, effort, and cost of creating object-oriented software systems, and improving their performance, quality and usability. To this aim, OOPS is seeking for research advances bringing benefits in all those typical aspects of software development, such as modeling, prototyping, design, implementation, concurrency and distribution, code generation, analysis, verification, testing, debugging, evaluation, deployment, maintenance, reuse, and software evolution and adaptation. The specific topics of interest for the OOPS track include, but are not limited to, the following: * Aspects and components * Code generation, and optimization, just-in-time compilation * Context-oriented programming * Databases and persistence * Distribution and concurrency * Dynamic and scripting languages * Evaluation * Feature Oriented Software Development and Programming * Formal verification * Internet of Things technology and programming * Integration with other paradigms * Interoperability, versioning and software evolution and adaptation * Language design and implementation * Modular and generic programming * Reflection, meta-programming * Runtime verification * Secure and dependable software * Static analysis * Testing and debugging * Type systems and type inference * Virtual machines OOPS offers a great opportunity to the OOP community to gain visibility, and to exploit the inter-disciplinary nature of SAC. - Submission Instructions Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2017 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2017 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authors' own related work should be in the third person. The format of the paper must adhere to the sig-alternate style. Full papers are limited to 6 pages with the option for up to 2 additional pages (max of 8 pages) at extra charge (80 USD per page). Posters are limited to 3 pages with the option for up to 1 additional page (max of 4 pages) at extra charge (80 USD). The length of the SRC abstracts is 2 pages with no additional pages at extra charge. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by October 7, 2016. For more information please visit the SAC 2017 home page. - Proceedings Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Paper registration is required, allowing the inclusion of the paper/poster in the conference proceedings. An author or a proxy attending SAC MUST present the paper. This is a requirement for the paper/poster to be included in the ACM/IEEE digital library. No-show of scheduled papers and posters will result in excluding them from the ACM/IEEE digital library. Student registration is only intended to encourage student attendance and does not cover inclusion of papers/posters in the conference proceedings. Finally, following the tradition of the past OOPS editions, depending on the quality and the overall number of accepted papers, authors of selected papers will be invited to submit an extended version for a journal special issue, after the conference.

1 0

Getting Pharo to Mars?
by phil＠highoctane.be Sept. 29, 2016

Sept. 29, 2016

Given http://waitbutwhy.com/2016/09/spacexs-big-fking-rocket-the-full-story.html we should find some way to get Pharo into it somehow. Anyone having ideas on how to do that? Phil

5 5

stdev
by stepharo Sept. 29, 2016

Sept. 29, 2016

Hi guys is stdev a typical name for standardDeviation? Because I found it sad to have mean and stdev instead of mean and standardDeviation. Stef

4 6

Tech Meeting notes
by stepharo Sept. 28, 2016

Sept. 28, 2016

Hi guys I tried to take some notes of the discussion and report of effort made by esteban VM works ======== - migrating our source to opensmalltalk vm 80% of our source - keybindings enhancement - shift key pressed - library symbols - change our cmake maker -> plain makefiles - port our process (running all the tests) - new VMs will get out - ARM VM is under dev and started to run. - migration planned for end of week of next weeks - right now able to build 32 and 64 on mac and linux. plan with mid october. - for windows - We will produce assert vm to help people to find problems. - Sierra support is coming. - openssl It will come after the end of the merge finished. - FFI bug about the Athens canvas. - FT bug is getting on the radar and esteban suspects that the bug is in the C plugin. We plan to throw away the FT plugin. If people want to help please have a look at thibaultRaffaillac bindings. - Pharo is using different VM functionalities so sometimes we are going on unfrequented paths. - Threaded FFI will come after 64, ARM, two bugs Probably beginning of the year. Iceberg ======== here is the log that nicolas sent to our internal mailing-list ### Last week: - Improved travis support, working on having all green tests in travis, still 4 to go. - Extending libgit support. - Support for synchronizing an Iceberg repository with code that was loaded with gitfiletree (was not working, as reported by Norbert). - Fixed some bugs (see https://github.com/npasserini/iceberg/milestone/7?closed=1) ### This week (starting 2016-09-26): - Finish having all tests running on travis. - Better management of ssh keys (which in turn is required for travis working correctly). - Also I would like to add some little GUI details that bother me in daily work (such as remembering common options, highlighting outdated repositories, or opening repositories from spotter). I think that this might take the whole week. After that I plan to add basic support synchronizing against code that was loaded from any repository. With that finished, we could release v0.3 After that, the plan for v0.4 is to make libgit our default backend, and make gitfiletree dependencies optional. - I am pretty close to have all tests running for libgit again, then we should try to use libgit as backend for the UI. But in that process also improve test coverage so that we minimize dependence on manual verification of the UI. - Remodularice in order to separate gitfiletree dependencies, so we will be able to use Iceberg without loading ossubprocess (or gitfiletree). - That will require also to write an independent cypress reader/writer, because the current one inherits from gitfiletree. If we have all this, I think that we could have a version that could be included in the base image, probably in the second half of october.

3 2

[pharo-project/pharo-core]
by GitHub Sept. 28, 2016

Sept. 28, 2016

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

1 0

[pharo-project/pharo-core] 90435d: 60242
by GitHub Sept. 28, 2016

Sept. 28, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 90435d4523791cb41cd1f4926638bdae4dc8eed2 https://github.com/pharo-project/pharo-core/commit/90435d4523791cb41cd1f492… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-28 (Wed, 28 Sep 2016) Changed paths: M AST-Core.package/NumberParser.class/instance/parsing-private/readExponent.st A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testFloatMaxAndMin.st M Kernel.package/Deprecation.class/definition.st A Kernel.package/Deprecation.class/instance/accessing/contextOfDeprecatedMethod.st A Kernel.package/Deprecation.class/instance/accessing/contextOfSender.st A Kernel.package/Deprecation.class/instance/accessing/context_.st M Kernel.package/Deprecation.class/instance/accessing/messageText.st R Kernel.package/Deprecation.class/instance/accessing/methodReference.st R Kernel.package/Deprecation.class/instance/accessing/method_.st R Kernel.package/Deprecation.class/instance/accessing/sendingMethodName.st R Kernel.package/Deprecation.class/instance/accessing/sendingMethodName_.st M Kernel.package/Deprecation.class/instance/comparing/=.st M Kernel.package/Deprecation.class/instance/comparing/hash.st M Kernel.package/Deprecation.class/instance/handling/transform.st A Kernel.package/Deprecation.class/instance/private/deprecatedMethodName.st A Kernel.package/Deprecation.class/instance/private/sendingMethodName.st M Kernel.package/Object.class/instance/deprecation/deprecated_.st M Kernel.package/Object.class/instance/deprecation/deprecated_on_in_.st M Kernel.package/Object.class/instance/deprecation/deprecated_on_in_transformWith_.st M Kernel.package/Object.class/instance/deprecation/deprecated_transformWith_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60241.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60242.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60241.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60242.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI-Tests.package/FFICallbackTests.class/definition.st A UnifiedFFI-Tests.package/FFICallbackTests.class/instance/support/wordResult_.st A UnifiedFFI-Tests.package/FFICallbackTests.class/instance/tests/testEnumerationReturnValue.st A UnifiedFFI.package/FFIExternalEnumerationType.class/instance/accessing/callbackReturnOn_for_.st Log Message: ----------- 60242 19145 FFI Callback return values for Enumerations should return their integer value https://pharo.fogbugz.com/f/cases/19145 19144 (FloatTest >> #testBinaryLiteralString) method cannot be compiled in latest image https://pharo.fogbugz.com/f/cases/19144 19132 simplify Deprecation class https://pharo.fogbugz.com/f/cases/19132 http://files.pharo.org/image/60/60242.zip

1 0

UFFI #isPointer - absolute or versus naturalPointerArity
by Ben Coman Sept. 28, 2016

Sept. 28, 2016

First, my C is a bit rusty so a question about semantics... int * a; typedef int * MyInt; MyInt b; So obviously the type of 'a' is a pointer, but is the type of 'b' a pointer? My intuition is that its not, since the pointer is wrapped inside the type. Now in my UFFI tutorial http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-4-ast-walking-w… I have a callback that I've modified here adding the #inspect... acceptCallbackFn := FFICallback signature: #( CXChildVisitResult ( CXCursor cursor, CXCursor parent, CXClientData client_data)) block: [ :cursor :parent :clientData | client_data inspect. visitResult add: cursor kind item. aCXChildVisitResult value "@1" ]. This can be invoked by running #testVisitChildrenCallbackBreak and an inspector opens on an ExternalAddress instead of the expected CXClientData. FFIExternalObject subclass: #CXClientData instanceVariableNames: '' classVariableNames: '' package: 'Libclang' where the FFIExternalObject says... "A typical usage of me is to create a subclass, and then use that subclass name directly in function signatures ... By putting FFIExternalObject subclass ... as a return type into the function signature, we are telling the code generator to ***automatically*** convert the return value into an instance of a given class and initialize its handle to the value returned by the function." This decision to return ExternalAddress instead of CXClientData occurs here... FFIExternalObjectType(FFIExternalType)>>handle: aHandle at: index self isPointer ifTrue: [ ^ aHandle pointerAt: index ]. ^ self basicHandle: aHandle at: index since... FFIExternalType>>isPointer ^ self pointerArity > 0 and... FFIExternalObjectType(FFIExternalReferenceType)>>naturalPointerArity ^ 1 So this naturalPointerArity=1 represents the situation presented with the C code at the top. So should #isPointer consider only the absolute pointerArity, or should is be... FFIExternalType>>isPointer ^ self pointerArity > self class naturalPointerArity Indeed, if I do that, plus these two additions copied from FFIExternalStructure... FFIExternalReferenceType>>basicHandle: aHandle at: index ^ self objectClass fromHandle: aHandle. FFIExternalReference>>fromHandle: aHandle ^self basicNew setHandle: aHandle Now running #testVisitChildrenCallbackBreak opens an inspector opens on a CXClientData as expected. And all UFFI tests continue to run fine. One thing I found strange though was... FFIExternalStructureType>>naturalPointerArity ^ 1 I would have thought a struct's natural pointer arity was 0 ? wdyt? cheers -ben

2 1

[pharo-project/pharo-core]
by GitHub Sept. 27, 2016

Sept. 27, 2016

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

1 0