Support variable declarations in c

[mustapha-belbiad]

No description provided.

[pyccel-bot]

Hello again! Thank you for this new pull request 🤩.

Please begin by requesting your checklist using the command /bot checklist

[Farouk-Echaref]

Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:

• Write a clear PR description
• Add tests to check your code works as expected
• Update documentation if necessary
• Update Changelog
• Ensure any relevant issues are linked
• Ensure new tests are passing
• Update AUTHORS file

[Farouk-Echaref]

/bot run pr_tests

[EmilyBourne]

This is only valid in Python > 3.8.
3.8 only reaches end of life in November so we still support it. You can use:

Suggested change

	a : set[int] #pylint: disable=unused-variable
	a : 'set[int]' #pylint: disable=unused-variable

to get round this

[Farouk-Echaref]

/bot show tests

[pyccel-bot]

The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests when they are marked as ready for review:

• linux : Runs the unit tests on a Linux system.
• windows : Runs the unit tests on a Windows system.
• macosx : Runs the unit tests on a MacOS X system.
• coverage : Runs the unit tests on a Linux system and checks the coverage of the tests.
• docs : Checks if the documentation follows the numpydoc format.
• pylint : Runs pylint on files which are too big to be handled by codacy.
• pyccel_lint : Runs a linter to check that Pyccel's best practices are followed.
• spelling : Checks if everything in the documentation is spelled (and capitalised) correctly.
• pr_tests : Runs all the tests marked in bold.
• pickle : Checks that .pyccel files have been correctly generated and installed by the installation process.
• editable_pickle : Checks that .pyccel files have been correctly generated and installed by the editable installation process.
• pickle_wheel : Checks that .pyccel files have been correctly generated and packaged into the wheel.
• anaconda_linux : Runs the unit tests on a linux system using anaconda for python.
• anaconda_windows : Runs the unit tests on a windows system using anaconda for python.
• intel : Runs the unit tests on a linux system using the intel compiler.

These tests can be run with the command /bot run X (multiple tests can be specified separated by spaces), or with try V X to test on Python version V.

[Farouk-Echaref]

/bot run docs pylint pyccel_lint spelling

[Farouk-Echaref]

/bot run docs pylint pyccel_lint spelling

[Farouk-Echaref]

/bot run linux

[EmilyBourne]

@Farouk-Echaref 64249ca looks like a rather opaque solution to this problem and one that could cause problems in some situations. E.g:

class A:
    def A__method():
        pass

The only reason the renaming is done in ModuleHeader is because _print_ModuleHeader is called before _print_Module. If you change the order then you could simply change where the renaming is done