Re: Question: Combination of Access and Constraining

["John R. Strohm" <strohm@airmail.net>]

It can.

Some years ago, I had occasion to do a pixel blob coloring routine, in C,
that did 8-way connectivity.  The first version used a subroutine.  Runtime
was absolutely unacceptable for the application.  The call/return and
parameter passing time dominated.  The second version used a C macro, and
was fast enough.

I used a macro because I wanted the source code to be HUMAN-READABLE.
Physically inlining the code, without the macro, would have been a lot less
readable.

"Simon Wright" <simon@pushface.org> wrote in message
news:x7vd6lji3b8.fsf@smaug.pushface.org...
> Yuri <yuri@tsoft.com> writes:
>
> > I agree mostly, but there could be projects where performance is
> > critical.
> >
> > If rate of processing is low than performance is no issue. But if
> > say you process real-time video higher-performance processor may
> > make project cost-inefficient.
>
> Many programmes have some time-critical areas. But it's not common (in
> my experience) for something like parameter passing style to have much
> impact, unless it's completely bizarre (passing 1MB arreays by copy
> would count as bizarre!) More often it's very localized, and better
> algorithms will make much more difference.