# Flex compiler -- max of 128 errors at a time?

**URL:** <https://forum.kirupa.com/t/flex-compiler-max-of-128-errors-at-a-time/310576>\
**Category:** flash\
**Created:** [June 14, 2010, 4:55am UTC](https://forum.kirupa.com/t/flex-compiler-max-of-128-errors-at-a-time/310576 "2010-06-14T04:55:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anogar](https://avatars.discourse-cdn.com/v4/letter/a/ed655f/32.png) [@Anogar](https://forum.kirupa.com/u/Anogar)\
**Post date:** [June 14, 2010, 4:55am UTC](https://forum.kirupa.com/t/flex-compiler-max-of-128-errors-at-a-time/310576/1 "2010-06-14T04:55:58Z")

</div>

So, my team is in the middle of changing an API on the game we’re working on, and we’re bug squashing. It’s a lot of dumb stuff – we went from String object IDs to Numbers, that sort of thing. Annnyhow.

The ■■■■■■ compiler only throws some portion of the errors at a time, and I can’t see any logic to how it picks which classes to complain about. I bet there’s probably something like 400 errors in the project, but it’ll only show whatever classes it’s feeling like. Even worse, you can fix a few bugs in one class, then recompile to get an updated list – and that class isn’t on the list anymore! It’s obvious that bugs still exist, but it’s no longer reporting them.

BAH! :fight:

Driving me nuts. :hitman2: