From mint-bounce@lists.fishpool.fi Wed Aug 25 06:36:04 2010 Message-ID: <3ECB431D42DE408E8785987C6800318B@mercatus.local> From: "Jo Even Skarstein" To: References: <615292.138510512-sendEmail@descaro> In-Reply-To: <615292.138510512-sendEmail@descaro> Subject: Re: [MiNT] AES related question: How to keep track if my application Date: Wed, 25 Aug 2010 12:30:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "Helmut Karlowski" Sent: Wednesday, August 25, 2010 11:30 AM To: Cc: Subject: Re: [MiNT] AES related question: How to keep track if my application >> >> application-control. But I hope you use the improved version with the >> >> pointer instead of 33 parameters on stack? >> >> Where is this documented? I have never heard of it before. > > Are you sure? > > /* this is our special invention to increase evnt_multi performance */ > > int EvntMulti( EVENT *evnt_struct ); Ahh, this one! Yes, I even use it in all my programs. For some reason I thought you were talking about a version of evnt_multi that pass a pointer to the event-struct to the AES, instead of copying the parameters to the parameter block. Jo Even