Common mistakes of new Geos programmers


  1. EC coding to catch bugs Since Geos is multithreaded and unlocked memory blocks can be moved out from under a pointer, debugging memory scribbling is quite difficult. Become familiar with the EC routines that are available within Geos and use them liberally. When compiled as non-EC, these routines become empty stubs, so they won't impact the performance of the shipping version of your application.

    Related to this is stress testing your application with swat. By simply turning on many of the EC flags, you can find many bugs that would otherwise take days to find and duplicate. Here is a partial list of flags to set:

  2. General Memory LMem (chunk, huge array, DB, etc.)
    VMFiles Miscellaneous

  3. Variables

  4. Memory
  5. Threads
  6. Files
  7. UI and Generic object trees
  8. Localization
  9. Graphics
  10. Miscellaneous


Last modified: Mon Dec 22 16:55:20 PST

r*bettsteller#web*de ---- If you are not a robot replace * by . (dot) and # by @
Wenn Sie kein Roboter sind ersetzen Sie * durch . (Punkt) und # durch @ (Klammeraffe)
Datenschutzerklärung | Haftungsausschluss | Impressum | Privacy Policy (English) | Disclaimer (English)