Haven't changed AlgorithmProxy as that class will be deleted in the next PR

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Runs clang-tidy pass by ref across the codebase to fix-up various
warnings we are seeing in cppcheck

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Also updated class_maker.py

Apply change to insert export macros into class definition using cmake GenerateExportHeader
feature to 3 more projects: API, Crystal and CurveFitting
Have replaced DllExport with the cmake macro except in these places:

a) class templates - the definitions of class template member functions need to be in the
same unit as the declaration so dllimport gives a compilation error in the client code
(C2491 in VS) eg SingleValueParameter, SingleValueParameterParser
b) headers which are in a project but aren't included by any .cpp units in the project
eg IBackgroundFunction.h, ICatalogInfoService.h. In these cases I've removed the DLLExport
attribute completely

For the API target there were a couple of special cases\extras:

API has some conditional use of the extern keyword to control instantiation of template
classes. This has been inserted into the automatically created dllconfig.h using a cmake
switch that allows some custom content to be appended to the end of the file. Few of the
targets require this so I've added a boolean parameter to the wrapper function to handle
this GENERATE_MANTID_EXPORT_HEADER

I also had to add explicit include directories to PythonInterfaceCore where it imports an
API target header (in the unit ExtractWorkspace.h) without having API as a dependency

This commit removes the final header guard that had
been missed by the auto replacer.

re: #28200

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

when creating a new algorithm
re #28093

re #28093

This commit removes header guards from tcc files that was missed in search script

This change fixes a problem in Workbench when setting columns to YErr
Previously this only worked if all Y columns had an associated YErr column. If that
wasn't the case then the associations between Y and YErr cols got mixed up
I have saved the link between the YErr and Y column into the C++ table workspace
object via changes to ITableWorkspace and the Column class
I've also modified the model\view\presenter for the table workspace to set and get
the link via the ITableWorkspace interface
The code in marked_columns.py has been modified to remove the _add function because
the logic required for adding x, y and yerr was sufficiently different that trying
to push them through a common _add function was obscuring the code
Finally I've removed the labelindex from the ErrorColumn object in the python code
because it can be worked out on the fly (and I didn't want to have to save this also
into the C++ table workspace in addition to the linked column index)

As part of the test updates I have removed the test
TableWorkspaceDisplayModelTest.test_initialise_marked_columns_yerr_before_y_doesnt_mark_yerr
because we do require the ability to add a yerr column before the corresponding y column
The model gets refreshed whenever the C++ table workspace is updated (eg when the type of a column
is updated) as part of a replace_workspace call. The model __init__ function builds up the column
set left to right and a user may have set up a Y err column which is to the left of the corresponding
Y column.

Signed-off-by: Harriet Brown <harriet.brown@stfc.ac.uk>

This commit replaces all header guards in API with #pragma once

Previously an algorithm only appeared when a progress message came in
re #27077

Newer boost bind seems to be causing
compiler warnings on Windows. It's no
longer required now bind is in the STL.
Refs #16578

A user wishes to offset the pulsetime of an event based
on its wavelength so the offset for each event must be
different

It costs slightly more memory but only bytes per workspace
and it is far safer than trying to manage the arrays
properly with new/delete.