[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: const T& func() const;
From:       Nick Shaforostoff <shafff () ukr ! net>
Date:       2007-08-16 4:24:01
Message-ID: 200708160724.01681.shafff () ukr ! net
[Download RAW message or body]

> it's not possible to later change the function to return 
> a calculated (rather than stored) value.

> In fact, I was fairly sure we were going to go the other way and change 
> const T & -> T.

and what's the preformance impact?
i suggest to use 'const T&' in core classes or in cases where we know for sure that \
the data will be always cached (e.g. it is obvious that we don't want to parse whole \
file everytime we need its metaInfo)


[prev in list] [next in list] [prev in thread] [next in thread]