<rennj>
yeah well real world is messy, compared to the actual math
<rennj>
anyway thats oldskool'
<rennj>
we are well beyond the ideals
<rennj>
after 1995 things went incompatible
<rennj>
Stroustrup lists incompatibilities with C90/C95 in Appendix B.2 of "The C++ Programming Language", Special Edition (which is 3rd edition with some added material):
<rennj>
according to stackexchange
<rennj>
this was sacrilege in #openbsd, i took flak for these statements...heh
<rennj>
at least haiku has not banished me
<rennj>
talking about nix reproachable builds, or zfs CRC checksum on data, or chain of trust..didnt go over well either..how about dtrace being able to probe kernel 1000 of times per second
<rennj>
NIH! everywhere
<rennj>
not invented here
<rennj>
how about picking and choosing from the best, imitation in flattery and all
rennj has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
<jessicah>
rennj: heh, some people are too serious :p
rennj has quit [Ping timeout: 480 seconds]
AlienSoldier has quit [Quit: Vision[]: i've been blurred!]
rennj has joined #haiku
Molnija has quit [Ping timeout: 480 seconds]
rennj has quit [Ping timeout: 480 seconds]
xet7 has quit [Remote host closed the connection]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rennj has joined #haiku
rennj has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
rennj has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
botifico has quit [Remote host closed the connection]
<PulkoMandy>
In C++ implicit casts from void* to other pointer types are not allowed
<PulkoMandy>
Example thing that works in C but not C++: int* foo = malloc(1024);
<PulkoMandy>
So it's rare to find a C program that will compile to C++ without any changes
<PulkoMandy>
As for the changes in C99, most have been "backported" to current C++ versions, and now it's not uncommon for people to submit proposals to both language committees, so that the languages don't drift apart anymore whenever possible
<andreasdr[m]>
Oh, good morning.
netposit1ve has joined #haiku
mmu_man has joined #haiku
netpositive has quit [Ping timeout: 480 seconds]
netposit1ve is now known as netpositive
OscarL has joined #haiku
<OscarL>
x512[m]: Found some of my old /bin/poke sources. Did some minor cleanups, it builds on modern Haiku now.
<OscarL>
Still needs work (most likely to be broken for 64 bits, autocompletion is broken, etc)
<OscarL>
Still need to dig up some documentation in html format I had for it :-D
<andreasdr[m]>
What is /bin/poke actually for?
rennj has quit [Ping timeout: 480 seconds]
<OscarL>
andreasdr[m]: to read/write to memory locations (both virtual and physical)..
<OscarL>
to read/write to ISA style I/O ports...
<OscarL>
and also to PCI config space registers.
<andreasdr[m]>
Nice.
<andreasdr[m]>
Sounds like a security issue though to me?
<OscarL>
Only if you're root? :-P
<OscarL>
it is intended to help poke around hardware while working on drivers.
<OscarL>
not something for end users, really.
<OscarL>
it uses the /dev/misc/poke driver that has been part of Haiku since mid 2005... /bin/poke is the user-facing part that got lost (most likely in AxelD's email trash/spam folder :-D) at ends of 2005.
<andreasdr[m]>
Yes.
<andreasdr[m]>
Its a nice app to have.
<andreasdr[m]>
I remember
<andreasdr[m]>
Root could have this priviledges for sure.
rennj has joined #haiku
rennj has quit [Ping timeout: 480 seconds]
tuaris has quit [Quit: Leaving.]
dqk_ has joined #haiku
dqk has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
AlaskanEmily has quit [Remote host closed the connection]
<mmu_man>
wait, we still don't have a /bin/poke?
rennj has quit [Ping timeout: 480 seconds]
<OscarL>
mmu_man: I sent my version to AxelD in... 2005-12-31... either it was deemed unworthy, or it got lost in the mail :-D
<jessicah>
copied a bunch of code out of Appearances, ripped stuff out of settings window and mashed them together
<OscarL>
Reduce, reuse, recycle... also applies to software! :-P
sav10 has joined #haiku
<PulkoMandy>
jessicah: I think the preview should oe 3px taller to have a margin at the bottom (like the top and left)
rennj has joined #haiku
matt3 has joined #haiku
sav10 has quit []
rennj has quit [Ping timeout: 480 seconds]
<x512[m]>
OscarL: With some hacks it seems possible to use poke driver for connecting PCI devices to virtual machine.
<andreasdr[m]>
That sounds cool.
<OscarL>
nice :-)
<OscarL>
Would be cook to try on my old TV/FM tuner card
<OscarL>
s/cook/cool
<andreasdr[m]>
Yes
<OscarL>
(only got the drivers for that to manage the TV/FM tuner, and get analog audio out of it... but still)
DKnoto has quit [Ping timeout: 480 seconds]
DKnoto has joined #haiku
<x512[m]>
It will need tome trickery to get PCI DMA working. Dumb solution would be allocate contiguous region of physical memory and identity map it as guest RAM.
<x512[m]>
Less dumb solution would probably need guest assistance or IOMMU.
<x512[m]>
It can be used to test Linux kernel GPU drivers on Haiku.
HaikuUser has joined #haiku
HaikuUser has quit []
<OscarL>
I wish I was smart enough to help with any of that :-)
HaikuUser has joined #haiku
rennj has joined #haiku
<andreasdr[m]>
I second that.
HaikuUser has quit [Remote host closed the connection]
matt3 has left #haiku [#haiku]
<OscarL>
Diver: that's what I call fast response times! Thanks! :-D
rennj has quit [Ping timeout: 480 seconds]
sav10 has joined #haiku
rennj has joined #haiku
Diver has quit [Ping timeout: 480 seconds]
<OscarL>
time to get some sleep. See you later, folks.
<xoblite>
...even then it doesn't seem like the threads are running full steam as per Process Controller (?)
<xoblite>
one teapot is ~120 FPS in the same environment
<xoblite>
and 580-600 FPS on bare metal
<xoblite>
:)
<damex>
Nice. I'm getting ~60 fps on bare metal - a shitty 10 year old netbook
<xoblite>
yeah pretty good, and then still on an unsupported graphics card i.e. basic framebuffer only
<damex>
How do I change the default web browser in Haiku?
<xoblite>
FileTypes prefs iirc
<xoblite>
text / Website location
<xoblite>
however not all of the ported ones have registered as viewers I believe
rennj has joined #haiku
DKnoto has quit [Ping timeout: 480 seconds]
<xoblite>
bbl
xoblite has quit [Quit: Vision[]: i've been blurred!]
<damex>
Cheers xoblite
x10z has joined #haiku
vdamewood has joined #haiku
AtomoZero has joined #haiku
MajorBiscuit has joined #haiku
AtomoZero has quit [Quit: Vision[]: i've been blurred!]
HaikuUser has joined #haiku
HaikuUser is now known as FloppiTuna
FloppiTuna has quit [Quit: Vision[]: i've been blurred!]
gouchi has quit [Remote host closed the connection]
rennj has quit [Ping timeout: 480 seconds]
diver1 has joined #haiku
Diver is now known as Guest211
diver1 is now known as Diver
damex has quit [Quit: Vision[]: i've been blurred!]
Guest211 has quit [Ping timeout: 480 seconds]
Molnija has joined #haiku
TkTech has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
xoblite has joined #haiku
<xoblite>
@waddlesplash ?
rennj has quit [Ping timeout: 480 seconds]
<waddlesplash>
yes?
<xoblite>
Hey... sorry to disturb, but did you have an explanation for why my commits end up becoming ancestors of each other? (I'm quite new to git, using other tools for my other projects)
<xoblite>
I do the regular add-commit-push
<xoblite>
in short: what specifies the ancestry?
TkTech has joined #haiku
rennj has joined #haiku
rennj has quit [Ping timeout: 480 seconds]
<waddlesplash>
xoblite: every commit is an descendant of the previous one
<waddlesplash>
unless you actually get rid of the previous one somehow they're all dependents on one another
rennj has joined #haiku
<xoblite>
hmm ok
<Skipp_OSX_>
xoblite ancestry is determined by sha
<Skipp_OSX_>
in gerrit you can keep a ChangeId that goes on top of newest but once the patch is in it's determined by the sha. So commits become ancestors of each other when they descent from the sha.
<xoblite>
and "indirect ancestor" here means what exactly?
<xoblite>
Skipp_OSX_ OK
<Skipp_OSX_>
mean where?
<Skipp_OSX_>
I see teapots
<xoblite>
I've pushed Devices, Tracker, GLTeapot... hardly related but still "indirect ancestors"
<PulkoMandy>
"indirect ancestor" is gerrit specific, it means you modified one of the previous commits so the next one refers to a now outdated version
<xoblite>
is the relation chain reset at some specific point?
<Skipp_OSX_>
yeah I guess that means it wants you to sync
<PulkoMandy>
It doesn't really matter I think, we can rebase the changes (remove the "ancestry") from gerrit web interface
<Skipp_OSX_>
it shouldn't make a difference in practice
<PulkoMandy>
Yes, it is broken by git rebase which allows you to change the order, add or remove commits, etc
<xoblite>
ok thanks, but don't want to make life harder for you if I'm doing something wrong git-wise...
<PulkoMandy>
Not really for now. If you start having many patches in progress at the same time it's a good rdea to plan a bit how you want to organize them
OscarL has joined #haiku
<xoblite>
have had issues rebasing at times; maybe I should just get a fresh tree
<Skipp_OSX_>
I like the teapots
<xoblite>
Skipp_OSX_: Thanks!
<Skipp_OSX_>
imagine once we get some hardware 3d acceleration going
<OscarL>
I don't see any "Change-Id" on xoblite's changesets on gerrit...
<xoblite>
PulkoMandy: As you can probably tell I'm a bit all over the place right now, still learning by looking at different parts of the tree
<OscarL>
xoblite: did you forgot to copy the commit-hook script? "scp -p <login>@git.haiku-os.org:hooks/commit-msg "haiku/.git/hooks/""
<xoblite>
Skipp_OSX_: On bare metal I get 580-600 FPS for a single teapot, in a VM 120 FPS.
<PulkoMandy>
Gerrit is currently configured to accept commits without change-id, but with a warning
<PulkoMandy>
Last time I suggested changing that, there was some disagreement on the mailing list
<xoblite>
ok done now :)
<xoblite>
thank you all
<xoblite>
PulkoMandy: Btw, did you suggest I save the mid click commit until I have added what it is to be used for to facilitate review, or just make the current action "do nothing" in the meanwhile? :)
<OscarL>
The issue I see is that it is really easy to miss for first time contributors (and even some long-time ones, when working from a new clone). I still don't know how I manage to actualy NOT mess that one up with my first patch :-D
<xoblite>
yeah I was pretty sure I went through it all, but perhaps I missed that single line...
<xoblite>
or maybe I did it for the buildtools only ;)