00:00:00 --- log: started forth/21.04.15
00:03:08 --- join: MrMobius joined #forth
00:19:35 --- join: proteus-person joined #forth
00:44:29 --- quit: MrMobius (Read error: Connection reset by peer)
01:06:06 <veltas> KipIngram: Interesting
01:06:30 <veltas> Yeah there's nothing inherently wrong with that choice, obviously you need easy enough rules to remember whichever system you go with
01:06:48 <veltas> Easier than writing 1000000
03:08:34 --- join: gravicappa joined #forth
03:10:33 --- join: hosewiejacke2 joined #forth
04:06:48 --- quit: hosewiejacke2 (Ping timeout: 260 seconds)
04:15:05 --- join: f-a joined #forth
04:44:57 --- join: hosewiejacke2 joined #forth
04:53:20 --- quit: X-Scale` (Quit:  HydraIRC -> http://www.hydrairc.com <- Now with extra fish!)
05:12:57 --- quit: hosewiejacke2 (Ping timeout: 246 seconds)
05:28:27 --- join: X-Scale joined #forth
05:55:32 --- quit: f-a (Ping timeout: 252 seconds)
05:56:33 --- quit: gravicappa (Ping timeout: 240 seconds)
05:57:26 --- join: f-a joined #forth
05:58:25 --- join: gravicappa joined #forth
06:03:14 --- quit: rpcope (Ping timeout: 252 seconds)
06:05:37 --- quit: dave0 (Quit: dave's not here)
06:06:16 --- join: hosewiejacke2 joined #forth
06:08:39 --- join: rpcope joined #forth
06:12:48 --- quit: hosewiejacke2 (Ping timeout: 240 seconds)
06:13:38 --- join: tech_exorcist joined #forth
06:15:20 --- quit: rpcope (Ping timeout: 252 seconds)
06:20:59 --- join: rpcope joined #forth
06:21:56 --- quit: f-a (Quit: leaving)
06:41:52 <KipIngram> Yeah, I'm still a little tempted by the idea, but for the time being I'm let 'e' make the number floating point.
06:42:34 <KipIngram> I can just picture myself, though, being smugly happy at just having to write 1e9 in a definition instead of the ten-character 1000000000
06:42:59 <KipIngram> Given my fondness for short definitions.  :-)
06:44:37 <KipIngram> But then I'd have to decide whether to treat negative exponents with no . as an error or not.  Treating it as an error would be a little more "pure" (i.e., the . being absolutely required), but on the other hand 1e-3 has a perfectly clear meaning.
06:45:29 <KipIngram> Someone asked me about doubles the other day - it had occurred to me that I could let 'e' be the required item for floating point and then I could have doubles and floatingn point.
06:46:03 <KipIngram> I'm just not accustomed to having scientific notation be *required* though - I don't totally like that vibe.
06:48:00 <KipIngram> And finally the other thing that occurred to me was to have a clean point within the code where I have a "power of 10 floating point number," and then tack the use of the FPU to get a fully standard float on after that.  Then I'd have a system that provided some sort of floating point support even in the absence of floating point hardware.
06:48:12 <KipIngram> Make the FPU optional.
07:18:19 --- join: MrMobius joined #forth
07:21:00 --- quit: andrei-n (Quit: Leaving)
07:40:11 --- join: f-a joined #forth
07:54:15 --- join: Zarutian_HTC1 joined #forth
07:54:15 --- quit: Zarutian_HTC (Read error: Connection reset by peer)
08:40:19 --- join: Zarutian_HTC joined #forth
08:40:19 --- quit: Zarutian_HTC1 (Read error: Connection reset by peer)
09:10:00 <KipIngram> Well, this section of composition of forms in the LISP 1.5 primer is a little opaque.  I mean, I see exactly what they're wanting to get at, but the description is rather intricate - seems like it could have been made more clear.  I'm not sure this would have "taught me" this material if I didn't already have a sense of what was coming.  At least not without going through it extremely slowly and carefully.
09:33:18 --- join: hosewiejacke2 joined #forth
09:55:34 --- join: shmorgle joined #forth
09:55:34 --- quit: f-a (Read error: Connection reset by peer)
10:00:36 --- join: f-a joined #forth
10:06:19 --- quit: Zarutian_HTC (Ping timeout: 252 seconds)
10:24:01 --- join: Zarutian_HTC joined #forth
11:04:08 --- quit: hosewiejacke2 (Ping timeout: 240 seconds)
11:14:42 --- join: eli_oat joined #forth
11:14:58 --- quit: eli_oat (Client Quit)
11:42:14 --- quit: gravicappa (Ping timeout: 240 seconds)
11:44:17 --- join: gravicappa joined #forth
12:33:24 --- join: hosewiejacke2 joined #forth
12:35:09 --- quit: hosewiejacke2 (Remote host closed the connection)
13:21:12 --- quit: gravicappa (Ping timeout: 246 seconds)
13:47:08 --- quit: mtsd (Ping timeout: 240 seconds)
13:56:40 --- quit: f-a (Read error: Connection reset by peer)
13:59:30 --- join: dave0 joined #forth
13:59:53 <dave0> maw
14:00:23 --- join: f-a joined #forth
14:58:37 <KipIngram> Afternoon.
15:05:26 --- quit: tech_exorcist (Ping timeout: 265 seconds)
15:18:42 --- quit: Zarutian_HTC (Remote host closed the connection)
15:32:19 --- quit: f-a (Quit: leaving)
15:38:33 --- join: Zarutian_HTC joined #forth
16:10:31 --- join: Zarutian_HTC1 joined #forth
16:10:32 --- quit: Zarutian_HTC (Read error: Connection reset by peer)
16:13:51 --- nick: Zarutian_HTC1 -> Zarutian_HTC
18:30:04 --- join: boru` joined #forth
18:30:07 --- quit: boru (Disconnected by services)
18:30:09 --- nick: boru` -> boru
18:56:47 --- join: eli_oat joined #forth
19:30:11 --- quit: Zarutian_HTC (Read error: Connection reset by peer)
19:30:19 --- join: Zarutian_HTC joined #forth
19:32:15 --- quit: eli_oat (Quit: WeeChat 2.8)
19:50:26 --- quit: sts-q (Ping timeout: 252 seconds)
20:02:51 <KipIngram> Heh.  This LISP stuff - I see a pattern.  Need to do something new?  Just wrap another layer of (...) around what you already have.
20:03:40 <KipIngram> What prompted me to say that is label notation.
20:04:44 --- join: sts-q joined #forth
20:46:08 --- join: gravicappa joined #forth
22:34:29 --- join: mtsd joined #forth
23:15:08 <proteusguy> KipIngram, we were the first agile dev shop in SEAsia as far as I can tell. The techniques and mindset are absolutely powerful tools - but this abandonment of "architecture" is certainly nonsense. Comes mostly from the early XP crowd and people shilling the magic sugar water - mostly consultants who don't have project deliverable responsibilities.
23:21:37 <proteusguy> I
23:23:08 <proteusguy> I'm a fan of fixed length iterations, story cards, story points for estimating via planning poker, & TDD. But I also believe strongly in architecture. Main thing is to delay decisions as long as you can, push the hard stuff up front, always focus on delivering value and not over engineering. 
23:27:34 --- quit: joe9 (Ping timeout: 240 seconds)
23:31:53 --- join: joe9 joined #forth
23:59:59 --- log: ended forth/21.04.15