<div>
<div class="content wysiwyg-content">
I was just curious, I've inherited an application and I often see multiple mx:Script blocks in a single file. Sometimes they are separated:<br />
<br />
mx:Script<br />
mxml<br />
<br />
mx:Script <br />
mxml<br />
<br />
and sometimes it's one after the other<br />
<br />
mx:Script<br />
/mx:Script<br />
<br />
mx:Script<br />
/mx:Script<br />
<br />
Are there any reasons for this? More specifically, for performance/optimization? If there is no performance benefit, I'd like to consolidate all of the .as code together.
</div>
</div>


I was just curious, I've inherited an application and I often see multiple mx:Script blocks in a single file. Sometimes they are separated:

mx:Script
mxml

mx:Script 
mxml

and sometimes it's one after the other

mx:Script
/mx:Script

mx:Script
/mx:Script

Are there any reasons for this? More specifically, for performance/optimization? If there is no performance benefit, I'd like to consolidate all of the .as code together.

Multiple mx:Script blocks in a single mxml file?

Apache Flex is a highly productive, open source application framework for building and maintaining expressive web applications that deploy consistently on all major browsers, desktops and devices (including smartphones, tablets and television). It provides a modern, standards-based language and programming model that supports common design patterns suitable for developers from many backgrounds. Flex applications can be deployed to the Adobe Player in the browser, Adobe AIR on desktop and mobile devices or to native Android, iOS, Windows or Mac applications.