code logs -> 2016 -> Sat, 21 May 2016< code.20160520.log - code.20160522.log >
--- Log opened Sat May 21 00:00:45 2016
00:14 Crossfire [Z@Nightstar-r9lk5l.cust.comxnet.dk] has joined #code
00:15 mode/#code [+o Crossfire] by ChanServ
01:04 Derakon[AFK] is now known as Derakon
01:58 catadroid [catadroid@Nightstar-umb6kf.dab.02.net] has joined #code
02:04 Derakon is now known as Derakon[AFK]
02:48 catadroid` [catadroid@Nightstar-m95st2.dab.02.net] has joined #code
02:50 catadroid [catadroid@Nightstar-umb6kf.dab.02.net] has quit [Ping timeout: 121 seconds]
03:18 thalass [thalass@Nightstar-283.o7s.158.104.IP] has quit [Operation timed out]
04:09 Crossfire [Z@Nightstar-r9lk5l.cust.comxnet.dk] has quit [Ping timeout: 121 seconds]
04:11
<&McMartin>
"Linguists like ambiguity more than other people"
05:34 Derakon[AFK] is now known as Derakon
05:42 Kindamoody[zZz] is now known as Kindamoody
05:56 Derakon is now known as Derakon[AFK]
06:07 celticminstrel [celticminst@Nightstar-q0f7bb.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
08:08
< catadroid`>
Really?
08:08
< catadroid`>
And yes
08:30 Kindamoody is now known as Kindamoody|afk
08:56 catadroid [catadroid@Nightstar-m95st2.dab.02.net] has joined #code
08:56 catadroid` [catadroid@Nightstar-m95st2.dab.02.net] has quit [The TLS connection was non-properly terminated.]
08:59 catadroid` [catadroid@Nightstar-m95st2.dab.02.net] has joined #code
08:59 catadroid [catadroid@Nightstar-m95st2.dab.02.net] has quit [The TLS connection was non-properly terminated.]
09:17 catadroid [catadroid@Nightstar-oreau5.dab.02.net] has joined #code
09:18 catadroid [catadroid@Nightstar-oreau5.dab.02.net] has quit [[NS] Quit: Bye]
09:21 catadroid` [catadroid@Nightstar-m95st2.dab.02.net] has quit [Ping timeout: 121 seconds]
10:13 catadroid [catadroid@Nightstar-oreau5.dab.02.net] has joined #code
10:13 catadroid [catadroid@Nightstar-oreau5.dab.02.net] has quit [[NS] Quit: Bye]
12:24 * TheWatcher gets the first part of IKELOS PENNINE GREEN (aka 'Titor') working, now for the hard bit involving much rsync magic
12:27 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
13:35 thalass [thalass@Nightstar-283.o7s.158.104.IP] has joined #code
13:35 mode/#code [+o thalass] by ChanServ
14:52 macdjord [macdjord@Nightstar-ahbhn1.cable.rogers.com] has joined #code
14:52 mode/#code [+o macdjord] by ChanServ
14:53 celticminstrel [celticminst@Nightstar-q0f7bb.dsl.bell.ca] has joined #code
14:53 mode/#code [+o celticminstrel] by ChanServ
15:22 Crossfire [Z@Nightstar-r9lk5l.cust.comxnet.dk] has joined #code
15:22 mode/#code [+o Crossfire] by ChanServ
18:47 catadroid [catadroid@Nightstar-uha5gl.dab.02.net] has joined #code
19:10 Derakon[AFK] is now known as Derakon
19:12 crystalclaw|AFK is now known as crystalclaw
20:08 thalass [thalass@Nightstar-283.o7s.158.104.IP] has quit [Operation timed out]
20:34 thalass [thalass@Nightstar-283.o7s.158.104.IP] has joined #code
20:35 mode/#code [+o thalass] by ChanServ
20:39
<@ErikMesoy>
Hmmm. A dilemma arises: to initially write a god object with a squillion methods, or to initially guess at the classes+objects I will need for a finicky, unfamiliar project? Both will probably require major refactoring later on anyway.
20:40
<&McMartin>
The latter; it's easier to squish together smaller objects then disentangle a giant skein of dependencies.
20:40
<&McMartin>
That *said*
20:40
<&McMartin>
If there isn't an obvious breakdown into objects
20:41
<&McMartin>
I suggest the alternative design school of "a small number of types of data objects, and many functions that operate on them"
20:41
<&McMartin>
Rather than a profusion of classes and a small number of functions shared between them
20:43
<&McMartin>
The problem with god objects isn't really so much that they are not OO enough
20:43
<&McMartin>
It's that they're also sacrificing the notion of modules
21:21 thalass [thalass@Nightstar-283.o7s.158.104.IP] has quit [Ping timeout: 121 seconds]
21:29 crystalclaw is now known as crystalclaw|AFK
22:01 thalass [thalass@Nightstar-283.o7s.158.104.IP] has joined #code
22:01 mode/#code [+o thalass] by ChanServ
22:05 Kindamoody|afk is now known as Kindamoody
22:07 Kindamoody is now known as Kindamoody[zZz]
22:18 catadroid` [catadroid@Nightstar-s2rlao.dab.02.net] has joined #code
22:21 catadroid [catadroid@Nightstar-uha5gl.dab.02.net] has quit [Ping timeout: 121 seconds]
22:26 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
22:26 mode/#code [+qo Vornicus Vornicus] by ChanServ
22:46
<@ErikMesoy>
I feel I'm skimping on my argument-passing in favor of references that shouldn't work. What's going on here? Why is this allowed? When does it stop being allowed? Minimal example code. http://pastebin.starforge.co.uk/706
22:47
<@ErikMesoy>
This is what happens when I start thinking "Can I...", find that I can, and push to see just how much I can. >_>
22:50 thalass [thalass@Nightstar-283.o7s.158.104.IP] has quit [Ping timeout: 121 seconds]
23:00 thalass [thalass@Nightstar-283.o7s.158.104.IP] has joined #code
23:00 mode/#code [+o thalass] by ChanServ
23:01
<~Vornicus>
It's allowed because otherwise you have the issue that, in C, headers "solve"
23:06
<~Vornicus>
In C, symbols have to be defined before you refer to them in any context whatsoever, so you need headers. In Java it kind of figures out what the headers would be. In Python, like in most interpreted languages, it resolve symbols when they are encountered in execution, and not before.
23:13
<~Vornicus>
So in this case - the program only executes line 9 (as opposed to building it into bytecode) after executing line 14 and thus defining what Redshirt is.
23:25 crystalclaw|AFK is now known as crystalclaw
23:29
< simon_>
couldn't you even refer to something non-existent on line 9, and it would still first fail when executing line 14?
23:29
<~Vornicus>
Yep!
23:30
< simon_>
I never got why that was a feature.
23:32
<~Vornicus>
Because the alternatives are worse in a variety of ways.
23:58
<&ToxicFrog>
ErikMesoy: nit: you don't need any of those 'pass' statements
23:59
<@ErikMesoy>
I know. I write them as hinters for autoindenting.
23:59
<@ErikMesoy>
I also like them for the "function ends here" explicit marking sometimes.
--- Log closed Sun May 22 00:00:01 2016
code logs -> 2016 -> Sat, 21 May 2016< code.20160520.log - code.20160522.log >

[ Latest log file ]