File: tchost.h

package info (click to toggle)
qtads 2.1.6-1.1
  • links: PTS
  • area: main
  • in suites: stretch
  • size: 16,156 kB
  • ctags: 18,767
  • sloc: cpp: 133,078; ansic: 26,048; xml: 18; makefile: 11
file content (97 lines) | stat: -rw-r--r-- 2,783 bytes parent folder | download | duplicates (11)
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
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
/* $Header: d:/cvsroot/tads/tads3/TCHOST.H,v 1.2 1999/05/17 02:52:27 MJRoberts Exp $ */

/* 
 *   Copyright (c) 1999, 2002 Michael J. Roberts.  All Rights Reserved.
 *   
 *   Please see the accompanying license file, LICENSE.TXT, for information
 *   on using and copying this software.  
 */
/*
Name
  tchost.h - TADS 3 Compiler Host System Interface
Function
  The host system interface is an abstract interface to services
  provided by the compiler host system.
Notes
  
Modified
  04/22/99 MJRoberts  - Creation
*/

#ifndef TCHOST_H
#define TCHOST_H

#include <stdarg.h>
#include "tcerr.h"

/* ------------------------------------------------------------------------ */
/*
 *   Abstract Host Interface 
 */
class CTcHostIfc
{
public:
    virtual ~CTcHostIfc() { }

    /* 
     *   Display a message, taking varargs parameters.  The message is a
     *   UTF-8 string.  The message string is a printf-style format
     *   string.  This is used to display informational messages.  
     */
    void print_msg(const char *msg, ...)
    {
        va_list args;

        va_start(args, msg);
        v_print_msg(msg, args);
        va_end(args);
    }

    /* display a message with va_list-style varargs */
    virtual void v_print_msg(const char *msg, va_list args) = 0;

    /*
     *   Display a process step message.  These work the same as
     *   print_msg() and v_print_msg(), respectively, but display a
     *   message indicating a process step.  Some implementations might
     *   want to display process step messages in a special manner; for
     *   example, a GUI implementation might put the message in a status
     *   bar or similar type of display rather than intermixed with other
     *   messages.  
     */
    void print_step(const char *msg, ...)
    {
        va_list args;

        va_start(args, msg);
        v_print_step(msg, args);
        va_end(args);
    }

    /* display a process step message with va_list-style varargs */
    virtual void v_print_step(const char *msg, va_list args) = 0;

    /* 
     *   Display an error message.  These work the same way as print_msg()
     *   and v_print_msg(), respectively, but display error messages
     *   instead of informational messages.  Some implementations might
     *   want to direct the different types of messages to different
     *   places; for example, a stdio implementation may want to send
     *   print_msg messages to stdout, but print_err messages to stderr.  
     */
    void print_err(const char *msg, ...)
    {
        va_list args;

        va_start(args, msg);
        v_print_err(msg, args);
        va_end(args);
    }

    /* display an error with va_list arguments */
    virtual void v_print_err(const char *msg, va_list args) = 0;
};


#endif /* TCHOST_H */