implicit parallelism

<parallel>

A feature of a programming language for a parallel processing system which decides automatically which parts to run in parallel.

The best way of providing implicit parallelism is still (1995) an active research topic. The problem is to generate the right number of parallel tasks of the right size (or "granularity"). Too many tasks and the system gets bogged down in house-keeping, or memory for waiting tasks runs out, too few tasks and processors are left idle.

The best performance is usually achieved with explicit parallelism where the programmer can annotate his program to indicate which parts should be executed as independent parallel tasks.

Last updated: 1995-02-16

implicit type conversion

<programming>

(Or "coercion") The abilty of some compilers to automatically insert type conversion functions where an expression of one type is used in a context where another type is expected.

A common example is coercion of integers to reals so that an expression like sin(1) is compiled as sin(integerToReal(1)) where sin is of type Real -> Real.

A coercion is usually performed automatically by the compiler whereas a cast is an explicit type conversion inserted by the programmer.

See also subtype.

Last updated: 1997-07-28

Nearby terms:

implicationimplicit parallelismimplicit type conversionimplies

Try this search on Wikipedia, OneLook, Google


Loading