[Lazarus] Using FPC parser/tokenizer for code formatting

[Adem]

On 2010-05-31 16:01, Michael Van Canneyt wrote:
> On Mon, 31 May 2010, Adem wrote:
>> I am not a compiler author, so I do not wish to be arguing with 
>> experts; but, it's not as if we have both alternatives to measure and 
>> chose the best on the aggregate.
>>
>> I can see that it is expected to be slower and will need more memory; 
>> but, we don't know is how much slower and how much more memory it 
>> will need. And, whether these will be noticeable/bearable considering 
>> what we gey out of it.
> To that we can reply now: No, it will not be bearable.
> We get enough complaints about speed/memory use as it is.
> Any additional slowdown is therefor simply not an option.
:)

You will always get complaints one way or another all the time, you know 
it as well as I do, even though/if your product reaches the speed of 
light. This is a fact of life --one which is usually responded to with 
"get a better hardware".

[See all those OSes that are getting more and more memory hungry and 
slower according to some, yet people seem to want even more features 
that add to all those 'bad aspects'.]

I too find it sensible/easier to tell people not to do anything 
--especially it may turn out to involve me mentally or physically-- 
different. So, I can understand that. But, then I usually tell myself to 
cool down a little (and be less fanatical so to speak) at least when 
discussing the idea.

Of course, I cannot expect everyone to do the same, but it would be nice 
if some could lend a little more benefit of doubt than others and say 
something like "go ahead and do it, we'll decide if it's good enough 
--then, not now"..

-- 
Cheers,

Adem