Is there a way to use git in Squeak? If so, does anyone have real experience
doing so? Pharo and its libraries seem to be moving to git "for real" and I
wonder about the implications for cross-platform compatibility…
-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Squeak-Dev-f45488.html
Folks
Still we have mailOutBugReport inside Squeak, but is not clear (to me) how
to easily use inside the Debugger
So if someone have insights, wish to know
Edgar
@morplenauta
Hello Hilaire
I think your 7 posts
http://blog.drgeo.eu/tag/dynabook
about the concept and learning model associated with the Dynabook are
very helpful to see the way forward to use Squeak/Pharo/Cuis as an
environment/authoring system for dynamic media.
I particular as these posts also contain an analysis what could/should
be implemented.
--Hannes
P.S. I included the Cuis list as I assume some people there are also
interested in this. This does not imply that a discussion has to be
cc-ed to all lists because many are on more than one list.
On 8/11/18, Hilaire <hilaire(a)drgeo.eu> wrote:
> How can Dynabook and interest based learning can be related?
>
> http://blog.drgeo.eu/post/2018/Interest-based-learning
>
> Hilaire
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>
Eliot Miranda uploaded a new version of Tools to project The Trunk:
http://source.squeak.org/trunk/Tools-eem.829.mcz
==================== Summary ====================
Name: Tools-eem.829
Author: eem
Time: 15 August 2018, 7:59:01.758651 pm
UUID: a9d8d8b5-5dbd-4838-8c9d-d0ac6c99801e
Ancestors: Tools-cmm.828
Fix a typo and an unnecessary complication in cutBackExecutionToSenderContext
=============== Diff against Tools-cmm.828 ===============
Item was changed:
----- Method: Debugger>>cutBackExecutionToSenderContext (in category 'private') -----
cutBackExecutionToSenderContext
"When accepting a new version of a method which can't be simulated (i.e. a quick method) we
must cut back to the sender. But this is non-trivial. If the quick method has been reached via
+ a perform: (as it is when one uses Create to implement a method from an MNU) then the relevant
- a perform: (as it is when one uses Create toi implement a method from an MNU) then the relevant
arguments won't be on the stack and we can't simply proceed without crashing the VM."
| oldContext context sel |
oldContext := self selectedContext.
self down.
context := self selectedContext.
+ context pc: context previousPc.
- context jump: (context previousPc - context pc).
sel := context selectorToSendOrSelf.
sel numArgs = oldContext method numArgs
ifTrue:
[context push: oldContext receiver.
oldContext arguments do:
[:arg| context push: arg]]
ifFalse:
[context privRefresh; stepToSendOrReturn]!