docstring patches for RB*, STCompiler optimizing?

On the compiler/ code:

Would you accept patches (no commitments here, but) that add
docstrings to the public interface of the Refactory parsing
and
scanning classes?

Does STCompiler currently perform the optimizations
performed by the
primitive compiler accessible by
Behavior>>#compileString:,
Stream>>#fileIn etc.?  I cannot find any code that
would suggest it
would, but I am perhaps overlooking something.

-- 
Stephen Compall
http://scompall.no
candysw.com/blog


_______________________________________________
help-smalltalk mailing list
help-smalltalkgnu.org

http://lists.gnu.org/mailman/listinfo/help-smalltalk

Stephen Compall wrote:
> On the compiler/ code:
>
> Would you accept patches (no commitments here, but)
that add
> docstrings to the public interface of the Refactory
parsing and
> scanning classes?
>
> Does STCompiler currently perform the optimizations
performed by the
> primitive compiler accessible by
Behavior>>#compileString:,
> Stream>>#fileIn etc.?  I cannot find any code
that would suggest it
> would, but I am perhaps overlooking something.
>   
If you refer to peephole optimizations and combining
multiple bytecodes 
in one, that 's done automatically when you create a
CompiledMethod.  
Methods such as #compileWhileLoop: take care of optimizing
#whileTrue: 
etc.  The only missing optimization is the inlined version
of #to:do: 
and #to:by:do:.

Paolo



_______________________________________________
help-smalltalk mailing list
help-smalltalkgnu.org

http://lists.gnu.org/mailman/listinfo/help-smalltalk