<> <> <> <> <> <> DIRECTORY Rope USING [ROPE]; MachineProfile: CEDAR DEFINITIONS = BEGIN OPEN Rope; <<>> <> <<>> <.profile, or if not found, then Machine.profile. The purpose of the profile is to allow tailoring of the system based on the machine. The current catalogue of ways the Cedar can be parameterized may be found in the file MachineProfile.doc.>> <<>> <: RETURN, where value is either (1) a BOOL, (2) an INT, (3) a TOKEN, or (4) a ListOfTokens (for more details, see MachineProfile.doc). When Cedar is booted, rolledBack, or any file whose extension is "profile" is edited, the profile is parsed and a data structure which describes the information that was found in the profile is constructed. Comments (indicated using the standard "--" convention) can appear anywhere in the profile and will be ignored. The parsing will also ignore extra spaces or blank lines. Any errors or anomalies discovered when parsing or accessing the profile will cause diagnostics to be printed to the file MachineProfile.log. The user will be informed that problems have been encountered via the Message Window. In no case however will the system break.>> <<>> <> <<>> <> <<>> <> <<>> <> Boolean: PROC [key: ROPE, default: BOOL _ FALSE] RETURNS [value: BOOL]; Number: PROC [key: ROPE, default: INT _ 0] RETURNS [value: INT]; Token: PROC [key: ROPE, default: ROPE _ NIL] RETURNS [value: ROPE]; <:, i.e. effectively does an IO.GetRope[IDBreak]. If the first character encountered is ", then reads everything to the next matching ", and returns this as a single rope. >> ListOfTokens: PROC [key: ROPE, default: LIST OF ROPE _ NIL] RETURNS [value: LIST OF ROPE]; <> <> <> <<>> <> Line: PROC [key: ROPE, default: ROPE _ NIL] RETURNS [value: ROPE]; <> GetProfileName: PROC RETURNS [ROPE]; <> << >> END. <> <> <> <> <> <<>>