[02:21:31] ** thinkeryzu has left IRC (Read error: 104 (Connection reset by peer))
[02:25:11] ** thinkeryzu has joined us
[03:34:23] ** thinkeryzu has left IRC (Remote closed the connection)
[03:34:47] ** thinkeryzu has joined us
[04:59:52] [connected at Mon Nov  5 04:59:52 2007]
[04:59:52] <> *** Looking up your hostname...
[04:59:52] <> *** Checking ident
[04:59:52] <> *** No identd (auth) response
[04:59:52] <> *** Found your hostname
[04:59:52] <> *** Your host is clarke.freenode.net[clarke.freenode.net/6667], running version hyperion-1.0.2b
[04:59:54] [I have joined #peak]
[05:20:12] ** apoirier has joined us
[07:43:00] ** tav has left IRC (Read error: 110 (Connection timed out))
[07:51:28] ** thinkeryzu has left IRC (Remote closed the connection)
[08:00:08] ** thinkeryzu has joined us
[08:07:33] ** tav has joined us
[10:17:58] ** thinkeryzu has left IRC ("Leaving.")
[10:18:14] ** thinkeryzu has joined us
[11:54:53] ** pje has joined us
[13:32:13] ** apoirier has left IRC ("KVIrc 3.2.6 Anomalies http://www.kvirc.net/")
[18:07:51] <tav> pje: did you ever get around to implementing semantic support (eval/exec, &c.) to SCALE?
[18:08:02] <pje> nope
[18:08:23] <pje> never worked on it again after the hurricane, IIRC.  :)
[18:08:38] <tav> doh!
[18:09:18] <tav> could you give me pointers on how one might go about it?
[18:13:33] <pje> well, there's a detokenizer that converts the structures back to strings.
[18:27:00] <tav> pje: aha
[18:27:03] <tav> thx
[18:27:46] <tav> btw, i'm planning to do 2 things with this -- one is a config system and another is for pattern matching in sensors
[18:28:38] <tav> the idea behind pattern matching in sensors to have a subset of python which can do == >= tests and support basic python expressions, e.g. name.endswith('ing'), &c.
[18:29:13] <tav> given your works on rule-dispatch/peak-rules, is there a better way to do the pattern matching?
[19:02:34] <pje> Well, you could actually use RuleDispatch to implement the pattern matching.
[19:07:41] <tav> pje: haven't looked at the code in a while but does that aspect require having access to func_* attributes ?
[19:07:45] <tav> cos, thanks to you, i don't have them anymore ;p
[19:08:18] <pje> eh?
[19:21:31] <tav> hmz
[19:21:52] <tav> does the code do magic with bytecode?
[19:40:57] ** pje has left IRC (clarke.freenode.net irc.freenode.net)
[19:40:57] ** thinkeryzu has left IRC (clarke.freenode.net irc.freenode.net)
[19:40:57] ** tav has left IRC (clarke.freenode.net irc.freenode.net)
[19:40:57] ** coderanger has left IRC (clarke.freenode.net irc.freenode.net)
[19:40:57] ** pje has joined us
[19:40:57] ** thinkeryzu has joined us
[19:40:57] ** tav has joined us
[19:40:57] ** coderanger has joined us
[19:52:42] <pje> RuleDispatch?  not really; it compiles some stuff w/exec
[19:52:54] <pje> PEAK-Rules makes new code objects
[19:53:07] <pje> But both use inspect.getargspec() and such, which use func_* attrs
[19:59:13] ** pje has left IRC ("Client exiting")
[23:10:46] ** coderanger has left IRC (clarke.freenode.net irc.freenode.net)
[23:15:23] ** coderanger has joined us
[23:21:49] ** coderanger has left IRC (clarke.freenode.net irc.freenode.net)
[23:27:41] ** coderanger has joined us
[23:37:39] ** tav has left IRC (clarke.freenode.net irc.freenode.net)
[23:40:17] ** tav has joined us
[23:51:39] ** coderanger has left IRC (clarke.freenode.net irc.freenode.net)
[23:55:44] ** coderanger has joined us