#pentagram@irc.freenode.net logs for 27 Nov 2002 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:12:37] <-- Darke|zzZ has left IRC (saberhagen.freenode.net irc.freenode.net)
[00:18:21] --> Dominus has joined #pentagram
[00:29:50] --> GigDR has joined #pentagram
[00:35:04] <-- GigDR has left IRC ("enough for now")
[00:37:32] <-- Dominus has left IRC (Read error: 104 (Connection reset by peer))
[00:57:59] <-- Dark-Star has left #pentagram ()
[01:04:49] --> Kirben has joined #pentagram
[01:04:49] --- ChanServ gives channel operator status to Kirben
[02:07:28] --> Darke|zzZ has joined #pentagram
[02:08:42] --- Darke|zzZ is now known as Darke
[02:08:53] --- ChanServ gives channel operator status to Darke
[12:53:01] <-- Kirben has left IRC (Read error: 104 (Connection reset by peer))
[13:04:11] --> Kirben has joined #pentagram
[13:04:11] --- ChanServ gives channel operator status to Kirben
[13:38:36] --> Colourless has joined #Pentagram
[13:38:36] --- ChanServ gives channel operator status to Colourless
[14:04:50] --> Dominus has joined #pentagram
[15:34:40] <Darke> Colourless: Did we end up with a 'definitive' answer as to whether [BP+06h] was _always_ the 'this' pointer? (*boggles and quickly changes from the german remorse back to something understandable*) Or whether it was different for 'ordinal' functions?
[15:35:09] <Colourless> it always is in processes
[15:35:20] <Colourless> in routines it may not be
[15:36:14] <Colourless> as far as I am concerned routines are 'not' object orientated
[15:36:55] <Colourless> the 'this' pointer, or what would appear to be the this pointer is actually an arg to the function
[15:39:27] <Darke> Hmm... can you think of any 'quick' way to verify this? I'm thinking of in the context of a program that has a rudementary understanding of a single 'function' at a time currently.
[15:39:42] * Darke denies making the 'this' pun deliberatly. *grin*
[15:40:29] <Colourless> nope, you will need to know the context of usage for the arg
[15:40:52] <Colourless> the most obvious method is if it's pushed right before a spawn then it's a this pointer for sure
[15:41:05] <Colourless> or calli
[15:42:19] <Colourless> i think that we should perhaps have 2 calli instructions. one would be for processes type calls, the other would be for routine type calls
[15:42:34] <Colourless> doesn't really matter though
[15:42:55] * Darke lightbulbs! Or a push dword/push indirect/set info sequence!
[15:42:56] <Colourless> i can't think of any other simple method of working out what [BP+06] actually is
[15:43:08] <Colourless> yes
[15:46:16] <-- Kirben has left IRC (Read error: 104 (Connection reset by peer))
[15:48:17] <Darke> Which of course is almost entirely pointless, since I just verified that all 'push dword's before a push indirect reference [BP+06h]. *grin* Ah well, at least we know we can flag it as a 'this' right from the beginning of those functions. *grin*
[17:35:26] --- Darke is now known as Darke|zzZ
[18:36:33] --> wjp has joined #pentagram
[18:36:33] --- ChanServ gives channel operator status to wjp
[18:42:38] <-- Colourless has left IRC ("casts invisibility")
[22:27:01] <-- wjp has left IRC (saberhagen.freenode.net irc.freenode.net)
[22:27:01] <-- Dominus has left IRC (saberhagen.freenode.net irc.freenode.net)
[22:27:14] --> wjp has joined #pentagram
[22:27:14] --> Dominus has joined #pentagram
[22:48:20] --- Dominus is now known as Dominus|away
[22:54:51] --- Dominus|away is now known as Dominus
[23:25:04] <-- wjp has left IRC ("Zzzz...")
[23:55:44] --> Kirben has joined #pentagram
[23:55:44] --- ChanServ gives channel operator status to Kirben