File: mpc_debug.pm

package info (click to toggle)
ace 8.0.5%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 47,088 kB
  • sloc: cpp: 342,864; perl: 31,902; sh: 1,963; python: 532; yacc: 524; xml: 330; lex: 158; lisp: 116; makefile: 85; csh: 20; ansic: 19; tcl: 5
file content (57 lines) | stat: -rw-r--r-- 2,069 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
package mpc_debug;

# ************************************************************
# Description   : Scope for declaring useful checkpoints in MPC.
#
#                 This package defines a scope for defining do-nothing
#                 subroutines.  Names should suggest checkpoints in the
#                 execution of MPC, and the body of the function should
#                 be empty.  Calls to these functions can be inserted into
#                 various locations inside MPC source code, and a developer
#                 can set breakpoints on these functions to make it
#                 easier to hone in on checkpoints.
#
#                 If a call is useful, but should only be enabled
#                 during debugging (e.g., it's on a critical path and
#                 could negatively affect performance) then one can
#                 simply comment out the call.
#
#                 For ease in finding calls, please always fully scope
#                 the call, e.g., mpc_debug::chkpnt_blah();
#
# Author        : Chris Cleeland
# Create Date   : 14.Dec.2010
# ************************************************************

# ************************************************************
# Pragmas
# ************************************************************

use strict;

# Checkpoints
#
# Please follow convention and begin each checkpoint name with
# the string "chkpnt_".  Adherence will make it easier for
# another developer to locate all occurrences of checkpoints
# within code using a tool like `grep`.

# Called in Driver's processing of *Creators
sub chkpnt_pre_creator_load { }
sub chkpnt_post_creator_load { }
sub chkpnt_pre_creator_create { }
sub chkpnt_post_creator_create { }

# Called in special 'after' keyword processing
# in ProjectCreator::process_assignment
sub chkpnt_pre_after_keyword_assignment { }
sub chkpnt_post_after_keyword_assignment { }

# Called in Parser::read_file
sub chkpnt_pre_read_file { }
sub chkpnt_post_read_file { }

sub chkpnt_pre_parse_base_project { }
sub chkpnt_post_parse_base_project { }

1;