Message-ID: <463081444.30305.1408666541839.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30304_859557659.1408666541838" ------=_Part_30304_859557659.1408666541838 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Last metaprogramming feature we'll cover today: runtime mixins. = @Mixin allowed you to mixin new behavior to classes you owned and were desi= gning. But you could not mixin anything to types you didn't own. Runtime mi= xins propose to fill that gap by letting you add a mixin on any type at run= time. If we think again about our example of vehicles with some mixed-in ca= pabilities, if we didn't own James Bond's vehicle and give it some= diving ability, we could use this mechanism:=20 =20
One or more mixins can be passed as argument to the static mixin() metho= d added by Groovy on Class.