This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Possible change to gen* for splits


>     Actually, since I can do lookahead, how about:
> 
> 	"condition"
> 
> 	"&& reload_completed"
> 
>     That seems to better reflect the actual relationship of the two conditions.
> 
> I guess that works since it would be meaningless were there not a
> previous condition, but it seems sort of "odd" to me, though I can't say
> exactly why.  My concern is in picking a syntax where it's obvious the
> is some relation between the two conditions to somebody who might not
> have carefully poured through all the documentation.

Maybe it would be better if the "glue" were to appear outside of the 
double quotes.  Eg (though I haven't thought the implications of this 
particular syntax through):

	+"&& reload_completed"

The plus sign would indicate that the two sets of conditions should be 
concatenated together.  It would also enable other terms in the 
concatenation, eg +"|| some_other_constraint".

Doing it this way would avoid the need to try and parse part of the 
contents of the condition string -- which strikes me as error-prone.

R.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]