Unnamed repository; edit this file 'description' to name the repository. https://git.adelon.net/gf-core.git/atom?h=optimize 2018-07-22T07:04:07+00:00 2018-07-22T07:04:07+00:00 meng wong mengwong@pobox.com 2017-08-19T11:27:07+00:00 urn:sha1:8a14912ee3b692bc578465b6920575f5d7b11b4c Traditionally, GF_LIB_PATH points to something like `.../share/ghc-8.0.2-x86_64/gf-3.9/lib` and if you want prelude and alltenses and present, you add a `--# -path=.:present` compiler pragma to the top of your .gf file But if you are developing some kind of application grammar library or contrib of your own, you might find yourself repeating your library path at the top of all your .gf files. After painstakingly maintaining the same library path at the top of all your .gf files, you might say, let's factor this out into GF_LIB_PATH. Then you might then find to your surprise that GF_LIB_PATH doesn't accept the usual colon:separated:path notation familiar from, say, unix PATH and MANPATH. This patch allows you to define `GF_LIB_PATH=gf-3.9.lib:$HOME/gf-contrib/whatever/lib` in a more natural way. If you are an RGL hacker and have your own version of the RGL tree sitting somewhere, you should be able to have both paths in the GF_LIB_PATH, for added convenience. This minor convenience will probably lead to obscure bugs and great frustration when you find that your changes are mysteriously not being picked up by GF; so keep this in mind and use it cautiously. This caution should probably sit in the documentation somewhere. A subsequent commit will do that. If you use zsh, you can do this to quickly build up a big GF_LIB_PATH: % gf_lib_path=( $HOME/src/GF/lib/src/{api,abstract,common,english,api/libraryBrowser,prelude,..} ) % typeset -xT GF_LIB_PATH gf_lib_path 2014-10-28T14:58:43+00:00 hallgren hallgren@chalmers.se 2014-10-28T14:58:43+00:00 urn:sha1:f085b807ebe7fa1bb6f05e6324b3e90ef4f109e5 2014-10-22T15:45:52+00:00 hallgren hallgren@chalmers.se 2014-10-22T15:45:52+00:00 urn:sha1:6ee67cd04ffbce375d7f10e74a5d9eb742d6428d 2014-10-21T19:20:31+00:00 hallgren hallgren@chalmers.se 2014-10-21T19:20:31+00:00 urn:sha1:391b301881bee7de9580f2c6d819144161e6a51d This makes the documentation clearer, and can potentially catch more programming mistakes. 2014-10-21T14:42:31+00:00 hallgren hallgren@chalmers.se 2014-10-21T14:42:31+00:00 urn:sha1:3bfcfa157dc291e03bfb4db3baed8b0098d76f50 Included renamings: SourceGrammar -> Grammar SourceModule -> Module SourceModInfo -> ModuleInfo emptySourceGrammar -> emptyGrammar Also introduces a type synonym (which might be good to turn into a newtype): type ModuleName = Ident The reason is to make types like the following more self documenting: type Module = (ModuleName,ModuleInfo) type QIdent = (ModuleName,Ident) 2014-10-20T19:45:43+00:00 hallgren hallgren@chalmers.se 2014-10-20T19:45:43+00:00 urn:sha1:a9bc1160521a0196ab8407a565b7643fe649f6f6 2014-10-16T16:28:54+00:00 hallgren hallgren@chalmers.se 2014-10-16T16:28:54+00:00 urn:sha1:6375bacc73c5ba2f0dd660fab18b590506027822 2014-10-15T20:42:36+00:00 hallgren hallgren@chalmers.se 2014-10-15T20:42:36+00:00 urn:sha1:393dde2eb93a975442697c177dbb161e4300bea0 2014-08-20T17:47:08+00:00 hallgren hallgren@chalmers.se 2014-08-20T17:47:08+00:00 urn:sha1:21f429caf8c8cb4248457c16abaf0ad4f51c974a 2014-08-20T17:04:15+00:00 hallgren hallgren@chalmers.se 2014-08-20T17:04:15+00:00 urn:sha1:73310add9a549b58381f475eab5324a17a6b83dd I prefer small functions with descriptive names over large monilithic chunks of code, so I grouped the compiler passes called from compileSourceModule into funcitons named frontend, middle and backend. This also makes decisions about which passes to run clearly visible up front. Also made some small changes in GF.Compile.