[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] volatile in pgmspace.h ?
From: |
E. Weddington |
Subject: |
Re: [avr-libc-dev] volatile in pgmspace.h ? |
Date: |
Tue, 17 Jun 2003 15:12:20 GMT |
> On Mon, Jun 16, 2003 at 10:16:17PM +0000, E. Weddington
wrote:
> > As the macros "return" the byte being read from flash,
the
> > only way I see to do this would be another parameter
which
> > would hold a pointer to their address. I don't think
this
> > would buy the user any advantage then.
>
> We have macros here, not functions. So, you can return
the new
> pointer value in the same macro argument, by using a
simple C
> assignment - no pointers. Of course, this should only be
done
> in the _next macros, not in the normal ones.
>
> Marek
Unfortunately, that would assume that the argument to the
macro would be a variable. If the argument is a constant,
it wouldn't work.
Eric
- [avr-libc-dev] volatile in pgmspace.h ?, Dmitry K., 2003/06/14
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/16
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/16
- Re: [avr-libc-dev] volatile in pgmspace.h ?, Unknown, 2003/06/16
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/16
- Re: [avr-libc-dev] volatile in pgmspace.h ?,
E. Weddington <=
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/17
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/17
- Re: [avr-libc-dev] volatile in pgmspace.h ?, E. Weddington, 2003/06/17