gnupic: Re: [gnupic] Relocatable code and EXTERN


Previous by date: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Follow-up question to the thread about Ben's port of Brad's Lab2 to gpasm, Nicholas Robinson
Next by date: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Follow-up question to the thread about Ben's port of Brad's Lab2 to gpasm, Wojtek Zabolotny
Previous in thread: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Relocatable code and EXTERN, Iain Dooley
Next in thread:

Subject: Re: [gnupic] Relocatable code and EXTERN
From: John De Villiers ####@####.####
Date: 2 Jan 2006 21:11:12 +0000
Message-Id: <1136236249.4886.235.camel@bbj.inet>

On Mon, 2006-01-02 at 12:51, Iain Dooley wrote:
> incidentally, an interesting way i use to pass arguments is to define a 
> series of call macros that look like C function calls in my code so:
> 
> myFunctionLookingMacro arg1,arg2
> 
> takes arg1 and arg2 and puts them into externally defined locations in my 
> library code. this makes your assembly look a _lot_ like C without the 
> clock cycle overhead of using a software stack to pass arguments.

As long as you understand your own code in a years time.
I myself never got "into" C at all. Just about every other language, but
never C.

John


Previous by date: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Follow-up question to the thread about Ben's port of Brad's Lab2 to gpasm, Nicholas Robinson
Next by date: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Follow-up question to the thread about Ben's port of Brad's Lab2 to gpasm, Wojtek Zabolotny
Previous in thread: 2 Jan 2006 21:11:12 +0000 Re: [gnupic] Relocatable code and EXTERN, Iain Dooley
Next in thread:


Powered by ezmlm-browse 0.20.