> I suggest to improve the case distinction for the make (and environment)
> variable “COCCI” also by adjusting the document outline.
> * Empty string
> * Directory selection
> * File name specification
>
> See also:
>
> I got the impression that you are struggling with difficulties (for unknown
> reasons)
> around adding space characters at some places.
> How would you like to improve this situation?
Thanks for your concern,but i haven't struggled with anything.I think i'm used
to
adding space characters.
>>> Unfortunately, I stumble on the error message “replacement: already
>>> tagged token:
>>> C code context” then.
>
> This is what I would expect.
I came along different application imaginations.
> You could use one rule with an exists to put a position variable in the place
> where you
On Thu, 31 Oct 2019, Markus Elfring wrote:
> > Unfortunately, I stumble on the error message “replacement: already
> > tagged token:
> > C code context” then.
This is what I would expect. You could use one rule with an exists to put
a position variable in the place where you want to put
> Unfortunately, I stumble on the error message “replacement: already tagged
> token:
> C code context” then.
It might be that the transformation approach was too generic for
the implementation of the function “megasas_mgmt_ioctl_fw”.
>> @addition@
>> expression object;
>> @@
>> object = kzalloc(...)
>> ... when any
>> device_unregister(...);
>> out:
>> +kfree(object);
>> return ERR_PTR(...);
>
> There is no reason why a patch should be generated in this case.
We come along different software development views also for
