Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#18617 closed enhancement (duplicate)

Write a tool to check for modularity violations in Tor's codebase

Reported by: nickm Owned by: nickm
Priority: High Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: TorCoreTeam201604, tor-modularity
Cc: Actual Points:
Parent ID: Points: small/medium
Reviewer: Sponsor: SponsorS-can


It's easy to find out which C files look at symbols from which other C files. If we combine that with the ability to know which C files belong to which modules, and which functions should move to _other_ C files, we'll be in good shape for a low-impact redividing of our source code into well-considered modules, to further simplify our modulewise callgraph.

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by nickm

Owner: set to nickm
Points: small/medium
Status: newaccepted

comment:2 Changed 5 years ago by nickm

Keywords: TorCoreTeam201604 added

For March, I aim to have alpha code here. For april I aim to merge.

comment:3 Changed 5 years ago by nickm

Resolution: duplicate
Status: acceptedclosed

This is now merged into #18803.

comment:4 Changed 5 years ago by nickm

Keywords: tor-modularity added
Note: See TracTickets for help on using tickets.