Re: [Pharo-users] mentor question 1

2020-04-29 Thread Ben Coman
> but I do not have a clue what the aBlock is You say the method definition is... > linksTowards: anAddressdo: aBlock and then later indicate its called like this... > linksTowards: aPacket destinationAddressdo: [ :link | self send: aPacket

Re: [Pharo-users] mentor question 1

2020-04-25 Thread Richard Sargent
On Sat, Apr 25, 2020, 16:17 tbrunz wrote: > Richard, > > I don't think it was silly. I'm sitting here thinking to myself, "Wow, > that's creative... Pharo being Pharo, you can write applications that can > send *blocks* between nodes, not just *data*..." > I understand. I meant that in the

Re: [Pharo-users] mentor question 1

2020-04-25 Thread tbrunz
Richard, I don't think it was silly. I'm sitting here thinking to myself, "Wow, that's creative... Pharo being Pharo, you can write applications that can send *blocks* between nodes, not just *data*..." The concept of sending behaviors as well as data opens up some interesting and powerful

Re: [Pharo-users] mentor question 1

2020-04-25 Thread tbrunz
Roelof, The core concept (as I see it) is that each node in your simulated network will receive packets as the simulation progresses, and the nodes must do something with each packet they receive. In OOP, it often helps to think about the objects in terms of "their responsibilities". And by

Re: [Pharo-users] mentor question 1

2020-04-25 Thread Richard Sargent
On Sat, Apr 25, 2020, 15:50 tbrunz wrote: > Hi Richard, > > I looked the repo; he's defined 3 classes: one for packets, one for nodes, > and one for links. So yes, he instantiates links. Likely each node has a > collection of links (each of which leads to another node in the network). > The

Re: [Pharo-users] mentor question 1

2020-04-25 Thread tbrunz
Hi Richard, I looked the repo; he's defined 3 classes: one for packets, one for nodes, and one for links. So yes, he instantiates links. Likely each node has a collection of links (each of which leads to another node in the network). The application is to simulate a network by modeling it in

Re: [Pharo-users] mentor question 1

2020-04-25 Thread Richard Sargent
On Sat, Apr 25, 2020, 11:46 Roelof Wobben via Pharo-users < pharo-users@lists.pharo.org> wrote: > Op 25-4-2020 om 20:17 schreef Roelof Wobben: > > Op 25-4-2020 om 20:04 schreef tbrunz: > >> 1. 'loopback' is a node, just like 'source' and 'destination'. A > >> network is > >> a mesh of 'nodes'

Re: [Pharo-users] mentor question 1

2020-04-25 Thread Roelof Wobben via Pharo-users
--- Begin Message --- Op 25-4-2020 om 20:17 schreef Roelof Wobben: Op 25-4-2020 om 20:04 schreef tbrunz: 1. 'loopback' is a node, just like 'source' and 'destination'.  A network is a mesh of 'nodes' joined by 'links'.  Your Pharo program represents one of those nodes: It is the 'loopback'

Re: [Pharo-users] mentor question 1

2020-04-25 Thread Roelof Wobben via Pharo-users
--- Begin Message --- Op 25-4-2020 om 20:04 schreef tbrunz: 1. 'loopback' is a node, just like 'source' and 'destination'. A network is a mesh of 'nodes' joined by 'links'. Your Pharo program represents one of those nodes: It is the 'loopback' node. oke, so I can do : loopback :=

Re: [Pharo-users] mentor question 1

2020-04-25 Thread tbrunz
1. 'loopback' is a node, just like 'source' and 'destination'. A network is a mesh of 'nodes' joined by 'links'. Your Pharo program represents one of those nodes: It is the 'loopback' node. 2. The block in the #linksTowards:do: method is the action to take on a packet, depending on whether its

[Pharo-users] mentor question 1

2020-04-25 Thread Roelof Wobben via Pharo-users
--- Begin Message --- Hello, Im doing the OOP book written by Ducassse and im now stuck at the network-simulator. Code so far can be found here : https://github.com/RoelofWobben/Network-simulator Im stuck at 2 places 1) What for datatype is