00:00:00 --- log: started forth/20.09.20 00:14:54 --- quit: gravicappa (Ping timeout: 256 seconds) 00:46:04 --- quit: proteusguy (Ping timeout: 256 seconds) 00:46:33 --- quit: proteus-guy (Ping timeout: 272 seconds) 00:51:24 --- quit: _whitelogger (Remote host closed the connection) 00:54:24 --- join: _whitelogger joined #forth 00:58:13 --- join: proteus-guy joined #forth 00:58:19 --- join: proteusguy joined #forth 00:58:19 --- mode: ChanServ set +v proteusguy 01:39:53 --- quit: kori (Quit: WeeChat 2.8) 01:45:54 --- join: kori joined #forth 03:55:53 --- join: dave0 joined #forth 04:23:31 --- quit: dave0 (Read error: Connection reset by peer) 04:28:49 --- join: dave0 joined #forth 04:38:51 --- join: deesix_ joined #forth 04:39:32 --- join: dddddd_ joined #forth 04:40:47 --- quit: deesix (Ping timeout: 264 seconds) 04:41:59 --- quit: dddddd (Ping timeout: 264 seconds) 04:55:02 --- nick: dddddd_ -> dddddd 04:55:13 --- nick: deesix_ -> deesix 05:26:25 --- quit: dave0 (Quit: dave's not here) 05:44:06 --- quit: jsoft (Quit: Leaving) 05:46:00 --- join: gravicappa joined #forth 06:54:10 --- join: crab1 joined #forth 06:54:58 --- quit: Zarutian_HTC (Remote host closed the connection) 08:16:59 --- join: Zarutian_HTC joined #forth 08:23:52 --- quit: crab1 (Ping timeout: 258 seconds) 10:41:06 --- quit: Zarutian_HTC (Ping timeout: 240 seconds) 11:00:40 --- join: Zarutian_HTC joined #forth 11:17:59 --- quit: gravicappa (Ping timeout: 272 seconds) 11:18:20 --- join: gravicappa joined #forth 13:16:13 --- quit: Zarutian_HTC (Remote host closed the connection) 13:23:01 --- join: Zarutian_HTC joined #forth 13:28:51 --- quit: gravicappa (Ping timeout: 260 seconds) 13:49:30 --- quit: tabemann (Ping timeout: 260 seconds) 14:24:07 --- join: dave0 joined #forth 15:08:09 --- join: Zarutian_HTC1 joined #forth 15:09:39 --- quit: Zarutian_HTC (Ping timeout: 260 seconds) 15:11:12 --- quit: dave0 (Read error: Connection reset by peer) 15:16:29 --- join: dave0 joined #forth 15:17:23 --- join: tabemann joined #forth 15:33:13 --- quit: dave0 (Read error: Connection reset by peer) 15:38:26 --- join: dave0 joined #forth 17:49:45 --- quit: dave0 (Quit: dave's not here) 18:57:58 --- join: boru` joined #forth 18:58:01 --- quit: boru (Disconnected by services) 18:58:03 --- nick: boru` -> boru 20:05:00 --- quit: DKordic () 22:35:15 --- join: gravicappa joined #forth 22:50:24 tabemann: Why would you want to rewrite the code, just be able to relicense? 22:51:49 While I see GPL3 having some problematic aspects, if I'm just hacking on something on my own I don't mind building off GPL3-licensed code. 23:30:31 siraben, GPL-3 is the most vile and invasive license yet written. Anything it touches MUST be published in a GPL-3 license. Even Linus had pointed out how completely inappropriate it is for even the Linux kernel which is GPL-2. Ultimately, the license gives rights to CODE and not users or developers. It's insane. 23:31:28 You can't even run stuff on servers as SaaS with a single piece of it being GPL-3 without publishing the source code for everything on that server. Absurd and delusional license. We don't allow it in our environment under any circumstances. 23:31:54 It depends on your use case. I have no qualms about rewriting the software after trying it out for personal use. 23:32:37 That's your choice. But then by making it GPL-3, you've also eliminated everyone else's choice who may want to run your software. It's the elimination of other's choices that's the problem. 23:33:13 So it doesn't depend on the use case. GPL-3 is a one size invades everyone use case. It eliminates all other use cases. That's why it's evil. 23:33:16 Agreed. I would not license new software I write under GPL-3. 23:33:25 Agree to eliminating others choice* 23:34:02 remexre: Closest example I could find was https://madiot.fr/files/reportru.pdf , has an operational semantics for a WHILE-like language with procedures, the semantics uses a call stack. 23:37:19 (page 9) 23:38:26 Looks like the way the semantics is presented allows to account for stack size as well, so presumably in a language one could enforce statically that the stack ever exceeds a certain size. 23:38:51 "Thus to consider stack overflow – although this notion is arbitrary in such a toy language – one just need to add a predicate to consider the maximum length of the state used in a sequence of reduction" 23:42:04 siraben, fixing the max size of the stack is the only way I ever thought possible. I even considered elimination of the option of tail calls and requiring all loops to be recursive as a means of limiting how long a function could run without having to have a "gas" mechanism like ETH. It solves a lot of the situations but I haven't confirmed it catches them all. 23:43:06 proteusguy: elimination of the option of tail calls? isn't having tail-call elimination exactly what you want? 23:43:22 I think you mean non-tail calls should be removed 23:44:07 siraben, it is for performance absolutely. It's not if we want to make the maximum resources a cryptoledger contract can utilize so that we can guarantee termination or roll back at some bounded cost. 23:44:49 siraben, the goal here is to guarantee an ended of a function within an acceptable limit as an alternative to gas. 23:46:00 to offset potential performance costs I considered offering "memoization" of recursive calls so prior values could be looked up rather than recomputed. 23:48:55 Well, guaranteed termination is a pretty solved problem, strictly recursing on smaller terms does it. 23:49:11 Right. 23:59:59 --- log: ended forth/20.09.20