00:38.05 |
CIA-55 |
BRL-CAD: 03Cprecup 07http://brlcad.org * r4361
10/wiki/User:Cprecup/GSoC2012_progress: 17/08/2012 - introduced the
"graph" command and a subcommand |
01:05.56 |
starseeker |
brlcad: don't worry, I wasn't going to start
investigating it |
01:07.00 |
starseeker |
not that old is necessarily bad, but its
license has an advertising clause in it |
01:07.11 |
starseeker |
and I doubt it does anything we don't already
do for ourselves |
01:11.47 |
*** join/#brlcad merzo
(~merzo@75-1-133-95.pool.ukrtel.net) |
02:04.46 |
*** join/#brlcad merzo
(~merzo@155-101-132-95.pool.ukrtel.net) |
02:23.20 |
*** join/#brlcad louipc
(~louipc@archlinux/fellow/louipc) |
04:48.21 |
CIA-55 |
BRL-CAD: 03crdueck * r52117
10/brlcad/trunk/src/librt/primitives/bot/bot.c: fixed memory leak,
some other minor changes |
06:07.41 |
*** join/#brlcad archivist
(~archivist@host81-149-189-98.in-addr.btopenworld.com) |
08:10.15 |
*** join/#brlcad elf_
(~elf@p22.eregie.pub.ro) |
09:16.13 |
*** join/#brlcad stas
(~stas@82.208.133.12) |
09:19.32 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.107.42) |
09:29.02 |
*** join/#brlcad archivist
(~archivist@host81-149-189-98.in-addr.btopenworld.com) |
10:01.39 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.107.42) |
12:12.10 |
*** join/#brlcad Stattrav
(u3131@gateway/web/irccloud.com/x-hjgrpyembujljntd) |
13:39.26 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.107.42) |
14:33.16 |
*** join/#brlcad andrei
(~andrei@79.117.233.10) |
14:59.48 |
andrei |
hello! |
15:00.06 |
andrei |
aside of 0, what can I pass as a parameter for
a function using : void (*errlog) (char *msg). |
15:00.17 |
andrei |
I don t understand the type |
15:01.54 |
andrei |
<PROTECTED> |
15:05.52 |
andrei |
nevermind, fixed it. |
17:55.09 |
*** join/#brlcad archivist
(~archivist@host81-149-189-98.in-addr.btopenworld.com) |
18:06.29 |
*** join/#brlcad Yoshi47
(~jan@d24-204-236-81.home4.cgocable.net) |
18:08.20 |
*** join/#brlcad stas
(~stas@86.122.32.42) |
18:25.46 |
brlcad |
andrei: that's a function callback, it takes a
function as a parameter |
18:26.07 |
brlcad |
so you could pass printf, for
example |
18:26.43 |
andrei |
I did that :) |
18:27.44 |
brlcad |
cristina: it sounds like you didn't register
the command somewhere for archer |
18:28.24 |
brlcad |
i don't recall off the top of my head, but you
can try searching for a similar command such as
"facetize" |
18:28.55 |
brlcad |
andrei: I'm going to have a little bit of time
to review some patches this weekend -- which of yours should I
start with first |
18:29.26 |
andrei |
I think you should start with the test_rbtree,
it should be easiest to review ( even tho it has nothing to do with
the project) |
18:29.31 |
andrei |
and afterwards, the test units |
18:29.42 |
andrei |
I need to re-upload them |
18:30.23 |
andrei |
Speaking of re-upload, I introduced some code
duplication ( in some of the tests). For example, I needed the
callbacks from pkg.c for pkg_getclient |
18:30.26 |
andrei |
how should I proceed? |
18:33.13 |
andrei |
or I have a display function common to around
5 tests. Should I move that to pkg.h ? |
18:34.48 |
cristina |
brlcad: Hello, I looked over other commands
and registered in in the same folders |
18:35.06 |
cristina |
s/folders/files |
18:35.33 |
*** join/#brlcad stas
(~stas@188.24.40.47) |
18:46.30 |
*** join/#brlcad stas
(~stas@188.24.42.87) |
19:16.06 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.105.83) |
19:32.10 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.105.83) |
19:47.23 |
*** join/#brlcad ksuzee
(~ksuzee91@193.151.105.83) |
20:45.06 |
*** join/#brlcad merzo
(~merzo@155-101-132-95.pool.ukrtel.net) |
22:12.15 |
andrei |
brlcad : I finished re editing both unit tests
and the fixes, they should be ready to be reviewed / commited.
Aside of that there are two unit tests that aren't in patch format,
I need a bit of help with them. I can t unit test pkg_waitfor since
it doesn't end. |
22:12.58 |
andrei |
also, I m getting some pretty wierd memory
leaks on test_pkg_send and I don t know why, it just displays some
gibberish |
22:24.23 |
andrei |
There are some unit tests where there isn't a
bu_free after memory allocation. The reason is that the functions
contain it. |
22:50.07 |
andrei |
the best order for review is, I think :
red-black tree test -> unit tests -> pkg fixes |
23:29.34 |
*** part/#brlcad ksuzee
(~ksuzee91@193.151.105.83) |