- Aug
- 2,267
- 108
Hi,
A suggestion for v12.
TCC allows access to the Component Object Model (COM) via the SCRIPT, RUBY, etc. commands.
For example, if I want to access a function from a COM dll, created via VB5, I can call the following RUBY code;
from TCC as follows;
Using Microsoft PowerShell, I can run the following;
to extract the text from an HTTP document.
Having the ability to access the Component Object Model directly from the TCC prompt would eliminate the need to gain access to an Object via RUBY, PowerShell, etc.
I realize that TCC has been extended to allow calling functions from DLLs via @WINAPI, and to access Windows Management Instrumentation via @WMI, but an interface to the Component Object Model, or which is sometimes referred to as OLE Automation, would be an added benefit.
Joe
A suggestion for v12.
TCC allows access to the Component Object Model (COM) via the SCRIPT, RUBY, etc. commands.
For example, if I want to access a function from a COM dll, created via VB5, I can call the following RUBY code;
Code:
require 'win32ole'
jlc = WIN32OLE.new('JLCUtils.cmath')
puts jlc.PricePerPound(ARGV[0])
Code:
set jlc=%@execstr[ruby jlc.rb 4.39]
Code:
$ie = New-Object -ComObject InternetExplorer.Application
$ie.Navigate("http://www.jpsoft.com")
$ie.Document.Body.InnerText
$ie.Quit()
Having the ability to access the Component Object Model directly from the TCC prompt would eliminate the need to gain access to an Object via RUBY, PowerShell, etc.
I realize that TCC has been extended to allow calling functions from DLLs via @WINAPI, and to access Windows Management Instrumentation via @WMI, but an interface to the Component Object Model, or which is sometimes referred to as OLE Automation, would be an added benefit.
Joe