[Tcl-bugs] [ tcl-Feature Requests-924045 ] wider use of TclWordKnownAtCompileTime()

[SourceForge.net <no...@so...>]

Feature Requests item #924045, was opened at 2004-03-26 09:04
Message generated for change (Comment added) made by andreas_kupries
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360894&aid=924045&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 46. Bytecode Compiler
Group: None
Status: Open
Resolution: None
Priority: 8
Submitted By: miguel sofer (msofer)
Assigned to: miguel sofer (msofer)
Summary: wider use of TclWordKnownAtCompileTime()

Initial Comment:
TclWordKnownAtCompileTime() is currently only used in
compiling [return]; it should be valuable elsewhere in
the compiler, wherever tests like 
   if (tokenPtr->type == TCL_TOKEN_SIMPLE_WORD)
are made. 
It will allow compilation of scripts with a fair amount
of \uHHHH encodings in them, plus backslash-newline in
long literal strings.

----------------------------------------------------------------------

>Comment By: Andreas Kupries (andreas_kupries)
Date: 2006-10-05 11:24

Message:
Logged In: YES 
user_id=75003

I have now compared the two functions, i.e. "TclIsLiteral"
and "TclWordKnownAtCompileTime". The general logic used by
both to decide the issue is identical (I am very glad to see
this, as it means that my understanding of the Token types
is likely correct).

What "TclWordKnownAtCompileTime" does beyond "TclIsLiteral"
is to actually assemble the literal value, if requested.

Note: The tclpro checker has commands to decide literal-ness
 and for assembly of the actual literal as well, based on
the  token list structure returned by the commands of the
Tclparser package (exposing the core parser to the script
level). I wonder if something can be done to expose
'TclWordKnownAtCompileTime' as well.

I will remove my TclISLiteral form the patch for 8.5, and
for 8.4 I will rename my function, but keep the reduced API,
i.e. no assembly of a value, only deciding literalness.
However this way the 8.5 function can be seen as 'obvious'
extension of the conditional one going into 8.4 for TIP 211ng


----------------------------------------------------------------------

Comment By: Andreas Kupries (andreas_kupries)
Date: 2006-09-29 11:01

Message:
Logged In: YES 
user_id=75003

Oh, I have a TclLiteral function in the patch I wrote for
#86/#211. Miguel, I will send you the patch, and maybe I can
use TclWordKnownAtCompileTime as well. Notethat my patch is
against 8.4, not head.


----------------------------------------------------------------------

Comment By: miguel sofer (msofer)
Date: 2004-03-26 09:06

Message:
Logged In: YES 
user_id=148712

oops -this is an RFE, not a patch

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360894&aid=924045&group_id=10894