From 22ae350525ad97a25e7ee28f996dc4d369ba8f67 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Thu, 12 Sep 2024 12:57:16 -0600 Subject: [PATCH] Remove references to BlockMatrixArray from the documentation. This class was removed several releases ago. --- include/deal.II/fe/fe.h | 2 +- include/deal.II/lac/matrix_block.h | 18 ------------------ include/deal.II/lac/precondition_block.h | 15 ++++----------- include/deal.II/meshworker/assembler.h | 7 ++++--- 4 files changed, 9 insertions(+), 33 deletions(-) diff --git a/include/deal.II/fe/fe.h b/include/deal.II/fe/fe.h index eba358f775..a795c35e15 100644 --- a/include/deal.II/fe/fe.h +++ b/include/deal.II/fe/fe.h @@ -160,7 +160,7 @@ class FESystem; * done based on vector components, but based on the use of * @ref GlossBlock "blocks", * and the result is then used to substructure objects of type BlockVector, - * BlockSparseMatrix, BlockMatrixArray, and so on. If you use non-primitive + * BlockSparseMatrix, and so on. If you use non-primitive * elements, you cannot determine the block number by * FiniteElement::system_to_component_index(). Instead, you can use * FiniteElement::system_to_block_index(). The number of blocks of a finite diff --git a/include/deal.II/lac/matrix_block.h b/include/deal.II/lac/matrix_block.h index 987792e654..1602786f2d 100644 --- a/include/deal.II/lac/matrix_block.h +++ b/include/deal.II/lac/matrix_block.h @@ -75,24 +75,6 @@ namespace internal * This behavior allows us to store MatrixBlock objects in vectors, for * instance in MGLevelObject without extracting the #matrix first. * - * MatrixBlock comes handy when using BlockMatrixArray. Once the MatrixBlock - * has been properly initialized and filled, it can be used in the simplest - * case as: - * @code - * MatrixBlockVector > > blocks; - * - * ... - * - * BlockMatrixArray matrix (n_blocks, n_blocks); - * - * for (size_type i=0;i