View Single Post
Old 09-07-2020, 08:54 PM   #359
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by chaley View Post
I am surprised. In GPM a ';' is a statement separator, not a statement terminator. For if-then-else that means a ';' before 'else' or 'fi' is a syntax error. My suspicion is that your quick test was only on books with no series, in which case the interpreter swallows the 'then' part without verifying the syntax.
You're right. I just happened that the first screen worth of books didn't have a series. And I didn't scroll down as everything seemed to be working. I could see the errors when I scrolled down. Removing the semi-colon fixed it.
Quote:
BTW: the "field()" function is now inlined, directly executed by the GPM interpreter. That means that now there is little performance difference between using a local variable and using "field", where before a local variable was around 10 times faster.
Good to know. What about "raw_field()"? I probably use that as much as "field()".
davidfor is offline