[Orca-users] Pushing for a 1.0 release

[Cockcroft, Adrian]

SE is effectively a full C language interpreter, it is a dialect of C with a few things missing and a few extensions. All scripts are run through CPP at runtime, then interpreted. Its actually a 64bit C interpreter, and is very efficient at doing numeric and c-struct intensive computations without doing lots of string conversions. e.g. kstat data.

Adrian

-----Original Message-----
From:	orca-users-bounces+acockcroft=ebay.com at orcaware.com on behalf of David Michaels
Sent:	Wed 10/5/2005 9:19 AM
To:	orca-users
Cc:	
Subject:	Re: [Orca-users] Pushing for a 1.0 release
Cockcroft, Adrian wrote:

>Its the same as C, something like
>
>system("clearlicense >/tmp/cl");
>f = fopen("/tmp/cl","r")
>fgets(f...)
>strtok();
>
>you get the idea.
>
>If there is a logfile to be monitored, then you can look at the http access log monitor code for ideas.
>  
>

Oh, okay.  Fascinating.  I didn't realize just how much C-stuff could be 
done in SE files.  Pardon my ignorance, but - does it actually interpret 
this code, or does it compile it behind-the-scenes when SE is invoked?

Sadly, for ClearCase, there is no license log file.  I've concocted a 
rudimentary lathe^[^? bourne script to monitor the clearlicense output 
every X seconds, and spit out a FlexLM-format license log, for feeding 
into an analysis script I wrote for easy input into Excel, yadda yadda.  
As you can tell, the process is tedious and annoying--it would be 
fantastic for Orca to track this instead (or even in addition).

I'll tinker, and compare to Kai's approach (followup email), which is to 
just throw the data to a separate file using a perl script (or 
aforementioned bourne script), and add stuffs to orcallator.cfg.

Thanks!
--Dragon

_______________________________________________
Orca-users mailing list
Orca-users at orcaware.com
http://www.orcaware.com/mailman/listinfo/orca-users