On Fri, Feb 12, 2016 at 12:16 PM, Andre Vehreschild <ve...@gmx.de> wrote: > Hi all, > > it wasn't my intention to start such a big discussion for such a small > thing. Please stop this academic battle and get back to the issue at > hand: > > Thomas is examining a symbol, that > > - has come through the scanner, i.e., it adheres to the rules of > gfortran, especially it is known to be smaller than GFC_MAX_SYMBOL_LEN > > - is still a valid symbol. When gfortran's internal > composition/modification of symbols breaks this rule, we are done > earlier already. > > - its length is not changed in his routine. > > I was only trying to prevent an alloc/free for this small use case, > which should fit on the stack quite easily. The proposed alloca() call > has according to the documentation of libc some availability issues on > certain platforms, too. Therefore why not going with the fixed size > stack array and adding a check for possible overflow to it and be done?
Yes, I agree. That sounds like the best approach in this case. -- Janne Blomqvist
