Vote On A Distribution For Linux Benchmarking

[blackout23]

This poll makes me impression and explain why, this site is a very technical, very popular with users 'technical', which explains the success of Arch-Linux, but I am rather surprised Ubuntu so high as it is directed to a different target .
I apologize for my English.

Arch Linux isn't even on the list. The reason Manjaro has to most votes, is because someone spammed the pool on their forums and a bunch of 0 post guys voted for Manjaro. It gained 100 votes in 12 hours, before that and was way behind.

[Charlie68]

This poll makes me impression and explain why, this site is a very technical, very popular with users 'technical', which explains the success of Arch-Linux, but I am rather surprised Ubuntu so high as it is directed to a different target .
I apologize for my English.

[Akka]

why is that? How is having a jump in C++ terrible compared to when doing it in ASM?

In c++ you have a reasonable exceptions system. C on the other hand lack this. A very useful solution is goto. On the other hand goto is very light and fast and can be used in performance critical situation also in c:ish c++.

[boast]

and goto asm dump are ugly and sometimes insecure, im picky and pragmatic what can i say

why is that? How is having a jump in C++ terrible compared to when doing it in ASM?

[chrisb]

Did you miss the sarcasm tag?

That's actually from Wayland or rather Weston... But I knew some idiot would claim it is ugly just because I said it is from Mir. It is the handle_setmaster function in this file: http://cgit.freedesktop.org/wayland/...eston-launch.c

I just changed some names around to remove any hint that it is from Weston.

Well played sir, well played.

[jrch2k8]

So if it's Canonical's code it's horrible, if it's someone else's code it's cool. Got it.

nope if that code is in C is tolerable since control flow in ISO C is not exactly awesome compared to C++ RAII, on the other hand if that code were trully C++ would be horrible because RAII control flows are wayyyyyyyyy better, still i pragmatically don't consider goto a good way to go but as was pointed is only present in logging code not in logic code

[jrch2k8]

I think it is generally considered acceptable use of goto to use it in error management in c code? At least it is very common. I get the impression the use both in weston and wayland is this.

yeah i mean is not illegal or wrong per se, i mean i was trained and trained and trained again to consider this stuffs the ultimate evil :

1.) char[] <-- will summon beelzebub to your house
2.) goto <-- will kill my dog
3.) union -- uint/char[] <-- will rupture space time continuum

and goto asm dump are ugly and sometimes insecure, im picky and pragmatic what can i say

[Akka]

I checked Wayland repo also and it seems that it uses goto more than Weston does.

http://cgit.freedesktop.org/wayland/...c/connection.c 15 instances

http://cgit.freedesktop.org/wayland/...yland-client.c 7 instances

http://cgit.freedesktop.org/wayland/...c/wayland-os.c 2 instances

http://cgit.freedesktop.org/wayland/...yland-server.c 5 instances

http://cgit.freedesktop.org/wayland/.../wayland-shm.c 3 instances


I don't think you needed to report a big for this as it is not really an issue with using goto as long as you use it properly.

I think it is generally considered acceptable use of goto to use it in error management in c code? At least it is very common. I get the impression the use both in weston and wayland is this.

[jrch2k8]

I checked Wayland repo also and it seems that it uses goto more than Weston does.

http://cgit.freedesktop.org/wayland/...c/connection.c 15 instances

http://cgit.freedesktop.org/wayland/...yland-client.c 7 instances

http://cgit.freedesktop.org/wayland/...c/wayland-os.c 2 instances

http://cgit.freedesktop.org/wayland/...yland-server.c 5 instances

http://cgit.freedesktop.org/wayland/.../wayland-shm.c 3 instances


I don't think you needed to report a big for this as it is not really an issue with using goto as long as you use it properly.

well in my brain is burned goto is the last option unless the universe is about collapse and implode, even if i know goto is not illegal to use, i guess ill take some time and try to remove them and submit the patches

[jayrulez]

yes i did was 1 am my gmt when i replied but that in plain ISO C XX is tolerable and since weston is a toy i can understand is less rigid about this kind of stuff but when you put C++ i snapped seeing a goto

well the good news i checked most wayland code and is neat and goto free, so i suppose this was the kinda "is a toy code i don't care" i will report it as a bug either way in case someone wants to use weston for production later

I checked Wayland repo also and it seems that it uses goto more than Weston does.

http://cgit.freedesktop.org/wayland/...c/connection.c 15 instances

http://cgit.freedesktop.org/wayland/...yland-client.c 7 instances

http://cgit.freedesktop.org/wayland/...c/wayland-os.c 2 instances

http://cgit.freedesktop.org/wayland/...yland-server.c 5 instances

http://cgit.freedesktop.org/wayland/.../wayland-shm.c 3 instances


I don't think you needed to report a big for this as it is not really an issue with using goto as long as you use it properly.