[00:38:45] *** Quits: fotonzade (~photon@78.189.158.97) (Quit: Leaving) [00:39:03] *** Joins: fotonzade (~photon@78.189.158.97) [02:46:59] *** Quits: fotonzade (~photon@78.189.158.97) (Ping timeout: 240 seconds) [02:57:59] *** Quits: sirdancealot (~sirdancea@79.98.72.195) (Ping timeout: 240 seconds) [04:58:06] *** Joins: JuanDaugherty (~juan@98.4.124.117) [06:03:19] *** Quits: JuanDaugherty (~juan@98.4.124.117) (Quit: Hibernate, reboot, exeunt, etc.) [06:43:59] *** Quits: proteusguy (~proteus-g@49.228.96.62) (Ping timeout: 240 seconds) [06:49:55] *** Joins: proteusguy (~proteus-g@49.228.96.62) [10:19:54] *** Joins: sirdancealot (~sirdancea@79.98.72.195) [12:16:58] *** Quits: sirdancealot (~sirdancea@79.98.72.195) (Ping timeout: 240 seconds) [12:17:34] *** Joins: fotonzade (~photon@78.189.158.97) [13:03:15] *** Quits: fotonzade (~photon@78.189.158.97) (Quit: Leaving) [14:00:38] *** Joins: JuanDaugherty (~juan@98.4.124.117) [14:16:12] *** Quits: proteusguy (~proteus-g@49.228.96.62) (Ping timeout: 268 seconds) [14:27:21] *** Joins: dbamzie (53fe595a@gateway/web/freenode/ip.83.254.89.90) [14:27:52] hello [14:28:52] Problem: compilation does not end or takes forever [14:29:05] What could be the problem? [14:29:14] *** Joins: proteusguy (~proteus-g@2405:9800:b408:bc31:4a51:b7ff:fe38:d966) [14:31:54] tell us more about the case where it does not end [14:32:14] how long has it been running now? [14:32:47] also, i personally am curious about forever [14:55:43] *** Joins: fotonzade (~photon@78.189.158.97) [15:13:04] when I write PredVP np vp = {s= \\b => np.s ++ vp.verb.s !(VPres np.a b) ++ vp.comp }; in MiniGrammarXXX.gf [15:13:53] creating a table from Boolean to String but the B is used in the record to determine the value [15:16:15] How long should one wait for compilation to complete? [15:24:06] so when people talking about "looping" or an "infinite loop" they don't really mean the latter [15:24:57] in practice all computing is based on users, developers, etc. having implicitly quantifiable expectations about how long a process should take [15:26:01] in this case, it is clear that what you are calling infinite compiling is in fact in all likelihood an error in an expression which causes it's evaluation not to terminate [15:26:55] at some level, not the one you're operating at, it would be considered a breach for the software not the recognize the error and terminate or not begin the evaluation [15:27:12] *not to recog [15:32:30] *its [15:37:08] Thanks [15:37:30] np [15:50:56] *** Quits: JuanDaugherty (~juan@98.4.124.117) (Quit: Hibernate, reboot, exeunt, etc.) [16:27:54] I only have that kind of construction. How can I establish the offending code? [16:59:05] *** Quits: fotonzade (~photon@78.189.158.97) (Quit: Leaving) [19:05:03] *** Joins: fotonzade (~photon@78.189.158.97) [19:14:10] *** Joins: sirdancealot (~sirdancea@79.98.72.195) [19:15:54] *** Quits: dbamzie (53fe595a@gateway/web/freenode/ip.83.254.89.90) (Ping timeout: 260 seconds) [20:15:12] *** Joins: JuanDaugherty (~juan@98.4.124.117) [21:04:37] *** Quits: sirdancealot (~sirdancea@79.98.72.195) (Remote host closed the connection) [21:14:17] *** Joins: sirdancealot (~sirdancea@79.98.72.195) [21:17:37] *** Quits: fotonzade (~photon@78.189.158.97) (Quit: Leaving) [22:08:58] *** Quits: proteusguy (~proteus-g@2405:9800:b408:bc31:4a51:b7ff:fe38:d966) (Remote host closed the connection) [22:53:19] *** Joins: fotonzade (~photon@78.189.158.97)