Changeset 25553 in project
- Timestamp:
- 11/22/11 21:44:40 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
gazette/src/issues/21.wiki
r25551 r25553 247 247 == 4. Core Development 248 248 249 TODO: INCLUDE CHRISTIAN'S REPORT. 250 251 I need some blurb on this from people Who Know. 252 I'd like something on the scrutinizer and stability work that's been going on as well as the proposal to bug fix until r7rs 253 and then do Chicken 5.0. 254 255 http://wiki.call-cc.org/development-process 249 Since the last issue two main things happened in the chicken core: 250 Improvements to the scrutinizer and hand in hand to that so called 251 specialisation (or partial evaluation). What does this do? The first 252 lead to a flow analysis pass in the compiler. This made it possible to 253 give the programmer more hints at potential programming errors, such 254 as unused code, unreachable branches, and type misuses. The latter is 255 done by having a central database of core procedure types. It is 256 installed as types.db and has been there on your chicken system for a 257 quite a while now. With more improvements going on the false positives 258 (warnings about non-issues) are much fewer than before, also lots 259 additional procedures and types have been added. One example for this 260 are procedures using ports which is now even checked for the right 261 port type (input or output port). 262 263 Now that the flow analysis pass is already there it can also be used 264 to optimise code, usually resulting in omitting redundant code such as 265 superfluous type checks. In the end this should lead to faster code 266 altogether. Over the last months more and more specialisations have 267 been added. For more information on specialisation see the respective 268 section at 269 [[http://library.readscheme.org/page10.html|readscheme.org]]. 270 271 A couple of months ago the CHICKEN team has formalised the development 272 process a bit as can be seen on 273 [[http://wiki.call-cc.org/development-process|its wiki page]]. Others 274 already joined in the discussion of patches on chicken-hackers and you 275 are more than welcome to join in. 276 277 As more people are trying git checkouts, the question of how to 278 bootstrap a git checkout properly keeps reappearing on the mailing 279 list. So the steps are: 280 281 * Build a stable or development release 282 * Checkout chicken-core from git (see [[http://code.call-cc.org]]) 283 * Build a boot-chicken: {{make boot-chicken}} 284 * Use this chicken to build the real chicken: {{make CHICKEN=./chicken-boot}} 285 * Install the chicken and run tests: {{make install && make check}} 286 256 287 257 288 sparc64 258 mario, felix , ckeen259 lots of bug fixes, sparc64 support , scrutinizer fixes289 mario, felix 290 lots of bug fixes, sparc64 support 260 291 261 292 * On origin/master:
Note: See TracChangeset
for help on using the changeset viewer.