| 00:10.50 | *** join/#brlcad mihaineacsu (~mihaineac@92.85.193.65) |
| 02:13.24 | *** join/#brlcad mihaineacsu (~mihaineac@92.85.193.65) |
| 02:53.13 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 11:17.39 | *** join/#brlcad infobot (ibot@rikers.org) |
| 11:17.39 | *** topic/#brlcad is BRL-CAD || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || GCI winners: Jacob Burroughs and Peter Amidon! || GSoC 2014 selections are announced! Thank you to all we got to work with. Remember that SOCIS is coming up right around the corner and you don't need a summer of code to get involved with open source. |
| 11:39.26 | *** join/#brlcad albertcoder (~albertcod@103.30.81.139) |
| 13:02.42 | *** join/#brlcad luca79 (~luca@net-37-116-126-166.cust.vodafonedsl.it) |
| 13:07.35 | starseeker | brlcad: OK, if we're going to leave poly2tri as an external lib/algorithm rathern than "borg" it into our C libraries I can see that. However, that makes it *imperative* that someone who knows what they are doing with C++ error handling fix poly2tri the right way |
| 13:07.49 | starseeker | which I freely admit is not me |
| 13:08.42 | starseeker | I can try, but I'm starting from square one and the stakes are very high from a user perspective |
| 13:28.37 | Notify | 03BRL-CAD:starseeker * 62392 (brlcad/trunk/doc/docbook/system/man1/en/g-tankill.xml brlcad/trunk/doc/docbook/system/man1/en/g-var.xml): xmllint fixes |
| 13:28.44 | Notify | 03BRL-CAD:starseeker * 62393 brlcad/trunk/src/librt/primitives/hrt/hrt.c: set but unused error |
| 13:47.36 | Notify | 03BRL-CAD:starseeker * 62394 (brlcad/trunk/src/other/poly2tri/README.md brlcad/trunk/src/other/poly2tri/poly2tri/common/shapes.cc and 8 others): All right - if we're going to keep poly2tri separate as opposed to eventually merging it into BRL-CAD's libs (and the work the bitfighter folks are doing combining clipper and poly2tri suggests that's a good idea) then we shouldn't be ripping out references for pointers. |
| 13:47.39 | Notify | We need another way to make the error cases do something other than bring down the application. |
| 14:54.49 | *** join/#brlcad FreezingCold (~FreezingC@CPE602ad06bea2a-CM602ad06bea27.cpe.net.cable.rogers.com) |
| 15:12.57 | *** join/#brlcad Ch3ck_ (~localhost@195.24.220.134) |
| 16:13.51 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 16:43.35 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 16:51.20 | *** join/#brlcad Izakee (~Isaac@195.24.220.134) |
| 16:58.17 | Izakee | Hi brlcad |
| 17:07.17 | Izakee | ``Erik starseeker Seen the images of the wire frame ? |
| 17:32.16 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 17:33.59 | *** join/#brlcad pujani (~pujani@202.164.45.204) |
| 17:35.33 | *** join/#brlcad pujani (~pujani@202.164.45.204) |
| 17:37.07 | *** join/#brlcad pujani (~pujani@202.164.45.204) |
| 17:38.38 | *** join/#brlcad pujaniS (~pujani@202.164.45.204) |
| 17:40.33 | *** join/#brlcad pujaniS (~pujani@202.164.45.204) |
| 17:41.14 | pujaniS | sir what is meaning of VGR? |
| 17:41.27 | pujaniS | what is the use of VGR? |
| 17:42.05 | pujaniS | VGR is any speed, running time or any thing else? |
| 17:49.54 | pujaniS | ? |
| 17:53.32 | *** join/#brlcad ries (~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
| 18:14.59 | *** join/#brlcad gurwinder (75dcab2b@gateway/web/freenode/ip.117.220.171.43) |
| 18:22.13 | gurwinder | brlcad: hello |
| 18:24.13 | gurwinder | I want to export only x coordinate, which we get using (ell->a). But I want only x value of 'a' I searched in ell.c. But can't get appropriate solution. eg. in pov ray, sphere is give by center and radius. center is exported succesfully but radius not. (ell->a) gives x, y, z but i want only x. |
| 18:26.21 | gurwinder | brlcad: sorry for mistake. We get x, y, z values using (ell->a) in case: ell. I want only value of x |
| 19:03.40 | *** join/#brlcad pujani (~pujani@202.164.45.204) |
| 19:12.20 | *** join/#brlcad pujani (~pujani@202.164.45.204) |
| 19:13.39 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 19:41.22 | *** join/#brlcad pujaniS (~pujani@202.164.45.204) |
| 19:42.39 | *** join/#brlcad pujaniS (~pujani@202.164.45.204) |
| 19:45.11 | *** join/#brlcad pujaniS (~pujani@202.164.45.204) |
| 20:48.42 | brlcad | starseeker: the ptr vs ref is completely irrespective of being snarfed in and borgified. c++ added refs because it explicitly makes one entire category of crashes disappear. the issue really is just how to 1) not let poly2tri decide when to halt an application and 2) how to let the callee know when something is wrong |
| 20:48.58 | brlcad | removing the aborts is good for #1 |
| 20:50.56 | brlcad | could have also left the aborts and used sigaction() if we needed/wanted to keep them pristine |
| 20:52.15 | brlcad | the more complicated of the two issues is #2, as there are many possible options |
| 20:54.53 | brlcad | setting an int or enum code is probably the very simplest change possible, but then looking at the code, that may even already be happening, so removing the aborts/asserts (or setting up handlers) may be sufficient |
| 23:33.55 | clock | brlcad, is there some paid job on brl-cad which can be done remotely by a non-us national% |