| 00:45.42 | *** join/#qi-hardware fengling_ (~fengling@58.135.95.136) |
| 00:54.56 | *** join/#qi-hardware fengling_ (~fengling@58.135.95.136) |
| 03:41.08 | *** join/#qi-hardware sandeepkr (~sandeep@111.235.64.4) |
| 03:46.47 | DocScrutinizer05 | http://www.theregister.co.uk/2016/07/11/linus_torvalds_in_sweary_rant_about_punctuation_in_kernel_comments/ krhrhrhr |
| 03:48.33 | DocScrutinizer05 | ((very black)) indeed, what the heck is that? |
| 04:00.55 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:02.21 | wpwrak | (linus) nice. i find that "networking style" particularly offensive, too. good to see that it gets some flaming :) |
| 04:16.55 | DocScrutinizer05 | we just discussed nested comments in another channel |
| 04:17.40 | DocScrutinizer05 | interesting - it seems gcc supports nesting nowadays, while we agreed that originally neither Kernigan nor Ritchie had that idea |
| 04:18.45 | DocScrutinizer05 | which makes me wonder how that goes along with compatibility for old source code |
| 04:19.36 | DocScrutinizer05 | well, probably a /* comment /* like /* this*/ wouldn't compile at all in new gcc then, so at least it doesn't go unnoticed |
| 04:20.24 | DocScrutinizer05 | if only a single compiler error "comment not closed" gets thrown |
| 04:21.21 | DocScrutinizer05 | [2016-07-15 Fri 05:15:09] <furrywolf> actually, googling suggests gcc handles nested comments by default. |
| 04:21.23 | DocScrutinizer05 | [2016-07-15 Fri 05:15:20] <furrywolf> since there's a -W option to bitch at you for using them. |
| 04:26.32 | *** join/#qi-hardware sb0 (~lekernel@59.152.213.90) |
| 04:38.59 | DocScrutinizer05 | <DocScrutinizer05> I recall having a editor macro for that which did convert all /\(_*\)\* to /\1_\* and same for */, between a block that gets /* commented out */. And inverse for deleting a /*, until next */ which would also get deleted. "so /* this */ comment" would become: "/* so /_* this *_/ comment */' |
| 04:40.20 | DocScrutinizer05 | [2016-07-15 Fri 05:33:57] <DocScrutinizer05> I wonder what Linus would utter, seeing this ;-P |
| 04:51.27 | DocScrutinizer05 | most recent KiCAD in a VM, built yesterday (the VM also is a complete build environment): vagrant init Neo900-KiCAD http://neo900.files.dev-1.org/vagrantboxes/kicad_1920x1080__root-devuan_compile-kicad/kicad-xfce-devuan.box; vagrant up; #login compile, kicad (ETA for upload: now+2h) |
| 04:52.54 | DocScrutinizer05 | vagrant install: https://releases.hashicorp.com/vagrant/1.8.4/ https://www.vagrantup.com/docs/installation/ |
| 04:54.02 | DocScrutinizer05 | root login: root, devuan |
| 04:57.06 | DocScrutinizer05 | there's a shared dir ./kicad |
| 05:02.14 | *** join/#qi-hardware luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 07:22.58 | *** join/#qi-hardware sb0 (~lekernel@210006059234.ctinets.com) |
| 09:11.44 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |
| 10:18.18 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 12:36.19 | DocScrutinizer05 | http://tonylovesziva.tumblr.com/image/14115122875 |
| 13:00.37 | *** join/#qi-hardware fengling (~fengling@124.205.63.12) |
| 15:58.46 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |
| 17:23.52 | *** join/#qi-hardware pcercuei (~pcercuei@92.177.36.45) |
| 19:23.56 | *** join/#qi-hardware arossdotme (~zxy@host-78-151-185-153.as13285.net) |
| 20:01.01 | *** join/#qi-hardware kilae (~chatzilla@catv-162-034.tbwil.ch) |
| 20:06.53 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 21:12.31 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |
| 22:00.37 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |
| 23:13.15 | *** join/#qi-hardware doomlord (~textual@host81-147-72-23.range81-147.btcentralplus.com) |