diff options
author | Nathan Scott <nathans@redhat.com> | 2023-08-31 11:56:43 +1000 |
---|---|---|
committer | Nathan Scott <nathans@redhat.com> | 2023-08-31 14:13:16 +1000 |
commit | b74673fe37fd379fc350789e696470556776d815 (patch) | |
tree | cbe4f036962c439f9c07a9c96302f5908f6410b0 /netbsd/NetBSDMachine.c | |
parent | 214166a049c2a6ac454dbb37b85b04c039a6a17a (diff) |
Rename ProcessList to ProcessTable throughout
Following up with some discusson from a few months back,
where it was proposed that ProcessTable is a better name.
This data structure is definitely not a list ... if it
was one-dimensional it'd be a set, but in practice it has
much more in common with a two-dimensional table.
The Process table is a familiar operating system concept
for many people too so it resonates a little in that way
as well.
Diffstat (limited to 'netbsd/NetBSDMachine.c')
-rw-r--r-- | netbsd/NetBSDMachine.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/netbsd/NetBSDMachine.c b/netbsd/NetBSDMachine.c index c1e6f7ed..245b8231 100644 --- a/netbsd/NetBSDMachine.c +++ b/netbsd/NetBSDMachine.c @@ -129,7 +129,7 @@ Machine* Machine_new(UsersTable* usersTable, uid_t userId) { } void Machine_delete(Machine* super) { - NetBSDMachine* this = (NetBSDProcessList*) super; + NetBSDMachine* this = (NetBSDMachine*) super; Machine_done(super); @@ -266,11 +266,11 @@ static void NetBSDMachine_scanCPUFrequency(NetBSDMachine* this) { void Machine_scan(Machine* super) { NetBSDMachine* this = (NetBSDMachine*) super; - NetBSDProcessList_scanMemoryInfo(this); - NetBSDProcessList_scanCPUTime(this); + NetBSDProcessTable_scanMemoryInfo(this); + NetBSDProcessTable_scanCPUTime(this); if (super->settings->showCPUFrequency) { - NetBSDProcessList_scanCPUFrequency(npl); + NetBSDProcessTable_scanCPUFrequency(npl); } } |