diff options
| -rw-r--r-- | AUTHORS | 6 | ||||
| -rw-r--r-- | DEVELOPING | 8 | ||||
| -rw-r--r-- | README | 2 | ||||
| -rw-r--r-- | README.metakit | 6 | ||||
| -rw-r--r-- | README.utf-8 | 2 | ||||
| -rw-r--r-- | jim_tcl.txt | 10 |
6 files changed, 17 insertions, 17 deletions
@@ -11,7 +11,7 @@ DESIGN CREDITS: some of the idea inside Jim are the fruit of long discussions inside the Tclers chat room. The feedback of the Tcl -comunity in general, and of the members of the Tcl Core Team, was +community in general, and of the members of the Tcl Core Team, was very important to avoid mistakes: I used the great experience of this people as a test for some of the ideas I put into Jim. Bad ideas tend to be demolished in no time by good engineers. @@ -21,12 +21,12 @@ Also the following ideas are due to the following authors: - Jim locals were originally proposed by Miguel Sofer, I (SS) added the feature that make they similar to lexical scoped closures using capturing of the local variables value if no explicit - intialization is provided. + initialization is provided. - The [lmap] command is my (SS) design, but I incorporated inside the command an interesting idea of Donal K. Fellows that proposed that the [continue] command may be used to skip the accumulation of the - current-iteartion result, providing in one command the power of + current-iteration result, providing in one command the power of [map] and [filter] together. @@ -46,7 +46,7 @@ the project that is about to be started. The only thing that has to be taken care of is the project mode -- it should be "push mode". Once the project is created one must add a user that will actually -start commiting new files to the repo. It can also be done through the +start committing new files to the repo. It can also be done through the WWW interface, so nothing more is necessary. Once finished with setting up a project on the WWW panel, one can @@ -65,12 +65,12 @@ So for example for me it was: In order to add file we type "git add <file>". For remove, we do "git rm <file>". To remove all local changes that aren't in a repository you do "git -reset --hard HEAD". Once inserted, files have to be commited with "git commit +reset --hard HEAD". Once inserted, files have to be committed with "git commit -a". Once done with commits for today, "git push" can be used to propagate changes from your local disk to the remote repository. Right now you can verify whether this works by trying to clone your -project's repository somewhere else, this time using anonymount HTTP +project's repository somewhere else, this time using anonymous HTTP access: git clone http://repo.or.cz/r/jimtcl/wkoszek.git @@ -83,7 +83,7 @@ Jim-devel mailing list: http://jim.tcl.tk:8080/cgi-bin/mailman/listinfo/jim-devel -Patches prepared with the procedures presented abore are welcome. Before +Patches prepared with the procedures presented above are welcome. Before submitting patches, you can verify that your changes didn't bring any regressions to the Jim. In order to do so, sample regression tests have been implemented. You can execute them by typing: @@ -190,7 +190,7 @@ HISTORY "first Jim goal: to vent my need to hack on Tcl." And actually this is exactly why I started Jim, in the first days -of Jenuary 2005. After a month of hacking Jim was able to run +of January 2005. After a month of hacking Jim was able to run simple scripts, now, after two months it started to be clear to me that it was not just the next toy to throw away but something that may evolve into a real interpreter. In the same time diff --git a/README.metakit b/README.metakit index ce9830b..03880a2 100644 --- a/README.metakit +++ b/README.metakit @@ -39,7 +39,7 @@ state of the database to disk. CREATING VIEWS -------------- *Views* in Metakit are what is called "tables" in conventional databases. A view -may several typed *properties*, or columns, and contains homogenous *rows*, or +may several typed *properties*, or columns, and contains homogeneous *rows*, or records. New properties may be added to a view as needed; however, new properties are not stored in the database file by default. The structure method specifies the stored properties of a view, creating a new view or restructuring an old one @@ -74,7 +74,7 @@ The supported property types include: `subview` : This type is not usually specified directly; instead, a structure description of a nested view is given. `subview` properties store complete - views as their value, creating hierarchical data structures. When retreived + views as their value, creating hierarchical data structures. When retrieved from a view, a value of a subview property is a normal view handle. Without a `description` parameter, the `structure` method returns the current @@ -108,7 +108,7 @@ where `$cur` is a string of form `viewHandle!index`. Row indices are zero-based and may also be specified relative to the last row of the view using the `end[+-]integer` notation. -A dictionary containing all property name and value pairs can be retreived by +A dictionary containing all property name and value pairs can be retrieved by omitting the `propName` argument: cursor get $cur diff --git a/README.utf-8 b/README.utf-8 index 4f3cbd5..06b37f4 100644 --- a/README.utf-8 +++ b/README.utf-8 @@ -32,7 +32,7 @@ of the concept of a "character", while UTF-8 is an encoding of Unicode into bytes. Thus the Unicode codepoint U+00B5 is encoded in UTF-8 with the byte sequence: 0xc2, 0xb5. This is different from ASCII where the same name is used interchangeably between a character value -and and its encoding. +and its encoding. Unicode Escapes --------------- diff --git a/jim_tcl.txt b/jim_tcl.txt index 4c9553b..39c7984 100644 --- a/jim_tcl.txt +++ b/jim_tcl.txt @@ -1894,7 +1894,7 @@ clock If no format is supplied, "%c" is used. :: If +'boolean'+ is true, processing is performed in UTC. - If +'boolean'+ is false (the default), processing is performeed in the local time zone. + If +'boolean'+ is false (the default), processing is performed in the local time zone. +*clock scan* 'str' *-format* 'format' ?*-gmt* 'boolean?'+:: Scan the given time string using the given format string. @@ -4779,7 +4779,7 @@ aio +$handle *tty* ?settings?+:: If no arguments are given, returns a dictionary containing the tty settings for the stream. If arguments are given, they must either be a dictionary, or +setting value \...+ - Abbrevations are supported for both settings and values, so the following is acceptable: + Abbreviations are supported for both settings and values, so the following is acceptable: +$f tty parity e input c out raw+. Only available on platforms that support 'termios(3)'. Supported settings are: @@ -5062,7 +5062,7 @@ The optional 'zlib' extension provides a Tcl-compatible subset of the `zlib` com +*inflate* 'data' '?bufferSize?'+:: Decompresses a raw, Deflate-compressed stream. When the uncompressed data size is known and specified, memory - allocation is more efficient. Otherwise, decomperssion is chunked and therefore slower. + allocation is more efficient. Otherwise, decompression is chunked and therefore slower. +*gzip* 'string' '?-level level?'+:: Compresses a buffer and adds a gzip header. @@ -5271,12 +5271,12 @@ independently (but synchronously) of the main interpreter. +*interp*+:: Creates and returns a new interpreter object (command). - The created interpeter contains any built-in commands along with static extensions, + The created interpreter contains any built-in commands along with static extensions, but does not include any dynamically loaded commands (package require, load). These must be reloaded in the child interpreter if required. +*$interp delete*+:: - Deletes the interpeter object. + Deletes the interpreter object. +*$interp eval* 'script' ...+:: Evaluates a script in the context for the child interpreter, in the same way as 'eval'. |