| ??? 07/10/01 14:18 Read: times |
#13124 - RE: MOVX equivalent |
Hi Andy,
what do you want ? Want you stick on pure ANSI 'C' ??? Or want you use the 8051 with some different memory areas and need a mechanism to address any of these ? By the way, XDATA, PDATA are macros only. So it's easy portable to other memory architectures. Simple exchange the macro definitions in the header file. I think macros are also full ANSI like, isn't it ? Following my header definitions to make a syntax check on 8051 sources with Borland C, it works nice: #ifdef __TURBOC__ #define bit char #define xdata #define idata #define bdata #define pdata #define data #define code #define sfr char #define sbit char #define sfr16 int #define interrupt /##/ // comment #define _at_ ;/##/ #endif Peter |
| Topic | Author | Date |
| MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
| RE: MOVX equivalent | 01/01/70 00:00 | |
RE: MOVX equivalent | 01/01/70 00:00 |



