Do you have a pointer to the description of the new restrictions? This
essentially makes macros useless for a lot of purposes. Also, I suspect
there might be something else going on here, because RexxMethod1 and
wholenumber_t should most definitely be defined by that point.
Rick
On Mon, Jun 27, 2016 at 11:19 PM, Erico Mendonca <[email protected]>
wrote:
> >
> >Is the problem with the token OPTIONAL_RexxStringObject? The fix could be
> a
> >simple as adding some additional defines for all of the OPTIONAL_* types
> at
> >the top of oorexxapi.h.
> >
>
> Not only that. In this call, for example:
>
> RexxMethod1(wholenumber_t, rexx_queue_queue,
> OPTIONAL_RexxStringObject, queue_line)
>
> GCC will complain about every one of the elements not being a valid token,
> like RexxMethod1, wholenumber_t, rexx_queue_queue...
>
> --
> — Erico Mendonça
>
> Dedicated Support Engineer
> SUSE
>
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
