Check-in [230d2e87e1]

Login
Bounty program for improvements to Tcl and certain Tcl packages.
Tcl 2019 Conference, Houston/TX, US, Nov 4-8
Send your abstracts to [email protected]
or submit via the online form by Sep 9.

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix markdown formatting issue
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk | minor change
Files: files | file ages | folders
SHA3-256: 230d2e87e13986ae39ea4be954b7b6904544d3ecd5052ffc6bbb03b8e2a0db3d
User & Date: dkf 2018-05-27 10:50:03
Context
2018-05-27
11:33
Minor editorial corrections to 431 formatting check-in: a4a3ebcbb3 user: dkf tags: trunk
10:50
Fix markdown formatting issue check-in: 230d2e87e1 user: dkf tags: trunk, minor change
10:43
A few more notes on exporting, and lengthen some very short paragraphs by combining them. check-in: a023e48805 user: dkf tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to tip/500.md.

266
267
268
269
270
271
272

273
274
275
276
277
278
279
280
name are:

 * “`::oo::Obj456`” — Fully-qualified instance namespace name; private
   variables are still ultimately variables that exist on object instances.
 * “`::`” — Namespace separator.
 * “`123`” — Declaring context ID, from the class that holds the definition of
   the private variable.

 * “` : `” — Private variable separator; a space, a colon, and another space.
   This is chosen to be very unlikely to be in user scripts by accident (as
   variable names with spaces and single colons are traditionally known to be
   awkward to use explicitly).
 * “`foobar`” — User-supplied variable name fragment.

Similarly, the **variable** method can be used to bring the private variable
into scope; this would not normally be necessary, but is useful when the usual






>
|







266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
name are:

 * “`::oo::Obj456`” — Fully-qualified instance namespace name; private
   variables are still ultimately variables that exist on object instances.
 * “`::`” — Namespace separator.
 * “`123`” — Declaring context ID, from the class that holds the definition of
   the private variable.
 * “<code> : </code>” — Private variable separator; specifically a space, a
   colon, and another space.
   This is chosen to be very unlikely to be in user scripts by accident (as
   variable names with spaces and single colons are traditionally known to be
   awkward to use explicitly).
 * “`foobar`” — User-supplied variable name fragment.

Similarly, the **variable** method can be used to bring the private variable
into scope; this would not normally be necessary, but is useful when the usual