Author: coke
Date: Mon May 5 22:09:23 2008
New Revision: 27331
Modified:
trunk/languages/tcl/README.pod
trunk/languages/tcl/TODO
trunk/languages/tcl/docs/hacks.pod
Log:
[Tcl] all tickets worth saving have been moved over to google.
Modified: trunk/languages/tcl/README.pod
==============================================================================
--- trunk/languages/tcl/README.pod (original)
+++ trunk/languages/tcl/README.pod Mon May 5 22:09:23 2008
@@ -12,6 +12,11 @@
../../parrot tcl.pbc foo.tcl
+You can also generate a faux-executable with C<make tclsh>; You could then
+run examples with simply:
+
+ ./tclsh
+
=head2 Interactive tclsh
To run partcl interactively, type:
@@ -31,7 +36,7 @@
Analagous to perl's C<-e> switch, this option will let you specify tcl
code in the command line, which will then be executed. e.g:
- $ ../../parrot tcl.pbc -e 'puts {Hello World}'
+ $ ../../parrot tcl.pbc -e "puts {Hello World}"
Hello World
You will need to properly quote the tcl to protect it from your shell.
@@ -49,13 +54,14 @@
=head2 Examples
-To run an example, change to the C<examples>, and type C<make>
+To run an example, change to the C<examples> directory, and type C<make>
for instructions.
=head2 Test Suite
To run the test suite, type C<make test>. If any tests fail, try
-C<TEST_PROG_ARGS=-G make test>. Send the results of both to the mailing list
+C<TEST_PROG_ARGS=-G make test>, which will disable parrot's garbage
+collection system. Send the results of both to the mailing list
C<[EMAIL PROTECTED]>.
=head2 Documentation
Modified: trunk/languages/tcl/TODO
==============================================================================
--- trunk/languages/tcl/TODO (original)
+++ trunk/languages/tcl/TODO Mon May 5 22:09:23 2008
@@ -1,6 +1,2 @@
All bugs and todo items should be documented in partcl's issue tracker at:
http://code.google.com/p/partcl/issues/list
-
-Some tickets are still in parrot's RT system at:
-
- https://rt.perl.org/rt3/NoAuth/parrot/List.html?Field=Lang&Value=tcl
Modified: trunk/languages/tcl/docs/hacks.pod
==============================================================================
--- trunk/languages/tcl/docs/hacks.pod (original)
+++ trunk/languages/tcl/docs/hacks.pod Mon May 5 22:09:23 2008
@@ -1,44 +1,22 @@
=head1 hacks.pod
-Prodding by Matt Diephouse to generate documentation for two things:
-
-=over 4
-
-=item 1
+=head1 WORKAROUNDS
Things that partcl has done that might be considered hacks -
things that will likely impair our ability in the distant future to
cleanly do language interoperability.
-=item 2
-
-Things that partcl hasn't done yet at all because parrot makes them
-hard.
-
-=back
-
-It is, of course, quite likely that said feature already exists with
-a nice interface, and was just not found by the partcl developers -
-If you find something along these lines, let them know on the internals
-list.
-
-=head1 WORKAROUNDS
-
=over 4
=item PDD20 - lexical vars
-The new scheme (PDD20) for lexical vars means that to use the 'store_lex', and
-'find_lex' opcodes, you have to be inside a sub that's marked :lex: That
-is, inside a sub that corresponds to a HLL block that introduces a new
-lexical scope. Tcl uses helper functions to figure out whether a particular
-'$a' is referring to a global or a lexical var. To keep our current
-flexibility, we keep track of the lexpads in the 'call_chain' variable and
-manually look up lexicals in the lexpads.
-
-This is in contrast to the previous way lexicals were implemented, which
-let you call the _lex opcodes anywhere, as long as at some point in the past
-of the program, you had a created a lex_pad and put it on the stack.
+The current scheme (PDD20) for lexical vars means that to be able use the
+'store_lex', and 'find_lex' opcodes, you have to be inside a sub that's
+marked C<:lex>: That is, inside a sub that corresponds to a HLL block that
+introduces a new lexical scope. Tcl uses helper functions to figure out
+whether a particular '$a' is referring to a global or a lexical var. We
+keep track of the lexpads in the 'call_chain' variable and manually
+look up lexicals in the lexpads.
=item subroutine meta information.
@@ -46,7 +24,7 @@
and their code. For example:
% proc sum {{a 2} {b 3}} {
- return [expr $a + $b]
+ return [expr $a + $b]
}
% sum
5
@@ -94,23 +72,12 @@
and, if any other languages support this feature, this would give us a chance
to interoperate.
-=item list splicing
-
-There are several cases where we convert TclLists or ResizablePMCArrays to
-Arrays so that we can use the splice opcode. Need to have better splice
-support in parrot array classes, as well as our own. See
-C<lib/commands/linsert.pir>.
-
=item flush diagnostics
-At the moment, there doesn't seem to be a parrot method for determining if
-a filehandled was opened for reading/writing. We can work around this by
+At the moment, there doesn't seem to be a parrot method for determining if
+a filehandle was opened for reading/writing. We can work around this by
tracking it in a hash in the _Tcl namespace.
-=item [after], [vwait]
-
-This is waiting, pending the event system re-thunk.
-
=back
=cut
