Update a configuration file: Difference between revisions

# This is a configuration file in standard configuration file format

#

# program. Blank lines are also ignored by the application program.

 

 

* [[Read a configuration file]]

<br><br>

 

=={{header|AutoHotkey}}==

data = %A_scriptdir%\rosettaconfig.txt

outdata = %A_scriptdir%\rosettaconfig.tmp

}

 

 

=={{header|C}}==

C with POSIX <code>strcasecmp</code> function for case-insensitive comparing. Substitute your toolchain's version.

 

#include <stdlib.h>

#include <string.h>

{ fprintf(stderr, "failed\n");

return (EXIT_FAILURE); }

 

Run:

=={{header|D}}==

This type of file is really not very suitable for automated management, so this code is very basic.

std.typecons;

 

cfg.addOption("numberofstrawberries", "62000");

cfg.store();

Input file:

<pre># This is a configuration file in standard configuration file format

NUMBEROFBANANAS 1024

NUMBEROFSTRAWBERRIES 62000</pre>

 

=={{header|Erlang}}==

Given the large number of very exact rules governing the update of this configuration file it is with some pleasure I add new options to the beginning of the file.

-module( update_configuration_file ).

 

[Option | T] = string:tokens( String, " " ),

string:join( [string:to_upper(Option) | T], " " ).

{{out}}

<pre>

 

=={{header|Fortran}}==

CHARACTER*28 FAVOURITEFRUIT

LOGICAL NEEDSPEELING

READ (F,FRUIT) !Read who knows what.

WRITE (6,FRUIT)

<pre>

&FRUIT

/

</pre>

 

 

 

But given that the NAMELIST protocol is available without difficulty, why would a hard-core fortranner bother for a Fortran programme?

 

=={{header|Go}}==

 

import (

c.Set("NUMBEROFSTRAWBERRIES", "62000")

c.Write(os.Stdout)

 

=={{header|J}}==

Since the task does not specify the line end character, we assume that the last character in the file is the line end character.

 

 

normalize=:3 :0

upd=. y,' ',":x

(<m) 1!:2~ normalize (,upd,{:);<@rxrplc~&(pat;upd) t

 

Note that, aside from the line end issue, the task is ambiguous because it specifies a set of operations rather than a file format. If the consequences of these ambiguities are troubling, you might prefer to replace normalize with normalize^:_

Example use:

 

'example.file' enable 'seedsremoved'

1024 'example.file' set 'numberofbananas'

 

Here's how the file specified in the task description looks after these steps have been executed:

{{trans|D}}

{{works with|Java|7}}

import java.util.*;

import java.util.regex.*;

}

}

 

Input file:

NUMBEROFBANANAS 1024

NUMBEROFSTRAWBERRIES 62000</pre>

 

=={{header|Lasso}}==

Config type definition

 

define config => type {

}

 

 

How to call it:

local(

config = config,

#config -> set('numberofbananas', 1024)

 

 

Initial config file:

NUMBEROFSTRAWBERRIES 62000

</pre>

 

=={{header|Perl}}==

 

use strict;

 

 

# How many bananas we have

 

 

 

 

 

 

 

 

 

 

 

}

 

 

=={{header|PicoLisp}}==

(in "config"

(make

(out "config"

(for L Data

 

=={{header|Python}}==

 

#----------------------------------------------------------------------------

cfg.enable_option('numberofstrawberries', 62000)

print cfg

 

Output:

Use the shared <tt>[[Racket/Options|options.rkt]]</tt> code.

 

#lang racket

 

;; numberofstrawberries with a value of 62000

(set! numberofstrawberries 62000)

 

=={{header|REXX}}==

 

Programming note: &nbsp; not all REXXes support the closing of files using the &nbsp; '''lineout''' &nbsp; BIF with a single argument.

parse arg iFID oFID . /*obtain optional arguments from the CL*/

if iFID=='' | iFID=="," then iFID= 'UPDATECF.TXT' /*Not given? Then use default.*/

cpy: call lineout oFID, arg(1); return /*write one line of text ───► oFID. */

dos: ''arg(1) word(arg(2) "2>nul",1); return /*execute a DOS command (quietly). */

'''output''' &nbsp; when using the default input file (which has additional removable statements) and input options:

<pre>

 

===version 2===

oid='updatecf.xxx'; 'erase' oid

options=translate('FAVOURITEFRUIT NEEDSPEELING SEEDSREMOVED NUMBEROFBANANAS numberofstrawberries')

done.option=1

End

{{out}}

same as for solution 'D'

 

=={{header|Ruby}}==

 

class ConfigFile

 

# How many bananas we have

outputs

<pre># This is a configuration file in standard configuration file format

=={{header|Tcl}}==

Creating this to be a general solution:

oo::class create Config {

variable filename contents

}

}

Applying to the task at hand (assuming a file in the current directory called <tt>sample.cfg</tt>):

$cfg disable needspeeling

$cfg enable seedsremoved

$cfg set numberofbananas 1024

$cfg set numberofstrawberries 62000

 

=={{header|TXR}}==

This works by reading the configuration into a variable, and then making multiple passes over it, using the same constructs that normally operate on files or pipes. The first 30% of the script deals with reading the configuration file and parsing each command line argument, and converting its syntax into configuration syntax, stored in <code>new_opt_line</code>. For each argument, the configuration is then scanned and filtered from <code>config</code> to <code>new_config</code>, using the same syntax which could be used to do the same job with temporary files. When the interesting variable is encountered in the config, using one of the applicable pattern matches, then the prepared configuration line is substituted for it. While this is going on, the encountered variable names (bindings for <code>var_other</code>) are also being collected into a list. This list is then later used to check via the directive <code>@(bind opt_there option)</code> to determine whether the option occurred in the configuration or not. The bind construct will not only check whether the left and right hand side are equal, but if nested lists are involved, it checks whether either side occurs in the other as a subtree. <code>option</code> binds with <code>opt_other</code> if it matches one of the option names in <code>opt_other</code>. Finally, the updated config is regurgitated.

 

@configfile

@(maybe)

@config

@ (end)

 

Sample invocation:

{{omit from|Lilypond}}

{{omit from|Openscad}}

 

=={{header|VBScript}}==

Set objFSO = CreateObject("Scripting.FileSystemObject")

 

Set objFSO = Nothing

Set objParamLookup = Nothing

 

{{In}}

 

{{Out}}

<pre>

# This is a configuration file in standard configuration file format