| 02:08.16 | *** join/#stepcode infobot (~infobot@rikers.org) |
| 02:08.16 | *** topic/#stepcode is STEPcode - data exchange with the technologies of ISO10303 || http://stepcode.org || LOG http://ibot.rikers.org/%23stepcode/ |
| 03:04.36 | *** join/#stepcode stirk (~charlie@c-71-56-216-45.hsd1.co.comcast.net) |
| 14:27.23 | *** join/#stepcode cwstirk (~charlie@c-71-56-216-45.hsd1.co.comcast.net) |
| 17:55.45 | *** join/#stepcode hoiji (3b5916ae@gateway/web/cgi-irc/kiwiirc.com/ip.59.89.22.174) |
| 17:58.01 | hoiji | mpictor: sorry just saw your reply in the logs couple of days back.. So currently we have 2 options... |
| 18:03.24 | *** join/#stepcode hoiji (75c953b3@gateway/web/cgi-irc/kiwiirc.com/ip.117.201.83.179) |
| 18:03.32 | hoiji | a) Use macros for toggling between thread safe and thread unsafe code |
| 18:03.51 | hoiji | b) Use different functions for thread safe & thread unsafe code. |
| 18:06.55 | hoiji | Personally speaking I would like to go with option (b) because I believe it will give more flexibility to the user, by allowing him to choose different version at different parts of his code (as suits him) |
| 18:16.55 | hoiji | Also, to answer mpictor question about feasibility of method (a): Yes the use of macros will also be quite state forward in this context. |
| 18:17.37 | hoiji | Do tell me which method should I go with? |