Quintasan | shadeslayer: ping | 00:07 |
---|---|---|
=== skreech_ is now known as Daskreech | ||
shadeslayer | Quintasan: pong | 01:30 |
Quintasan | shadeslayer: C question time | 01:31 |
Quintasan | shadeslayer: You can't return a whole array from a function, right? | 01:31 |
shadeslayer | sure you can :p | 01:32 |
Quintasan | wtf | 01:32 |
shadeslayer | hm, wait | 01:32 |
Quintasan | like | 01:32 |
shadeslayer | lemme check something | 01:32 |
Quintasan | int[1000] function(int x) ? | 01:33 |
Quintasan | impossible | 01:33 |
shadeslayer | typedef it | 01:33 |
shadeslayer | and then use the typedef as the return type | 01:34 |
shadeslayer | though I'm not sure if this will work | 01:34 |
shadeslayer | you'll have to try it out to check | 01:35 |
shadeslayer | so something like typedef int[100] myAwesomeArray; | 01:35 |
shadeslayer | and then myAwesomeArray function(int x) | 01:35 |
Quintasan | that's fucking retarded if I may say so | 01:36 |
shadeslayer | heh | 01:36 |
Quintasan | shadeslayer: Let's say my function returns a pointer to an interger | 01:37 |
shadeslayer | okay | 01:37 |
Quintasan | and that happens to point to beginning of an array | 01:37 |
shadeslayer | why not just point to the first element of the array | 01:37 |
Quintasan | that's what I did | 01:37 |
shadeslayer | or well, you can phrase that better by saying you're returning a pointer to the array | 01:37 |
shadeslayer | right, go on | 01:37 |
Quintasan | now, how the fuck do I iterate over that array without knowing it's size? | 01:37 |
Quintasan | I know I can increment the pointer | 01:38 |
Quintasan | but how the hell do I know when to stop? | 01:38 |
shadeslayer | do you know the size of one element in the array beforehand? | 01:38 |
shadeslayer | like, is it an array of int's? | 01:38 |
Quintasan | well yeah, it's an array of int's | 01:38 |
Quintasan | doing ptr+1 will actually do ptr+1*sizeof(int) | 01:39 |
shadeslayer | yeah so int is 4 bytes right? | 01:39 |
shadeslayer | heh | 01:39 |
shadeslayer | yeah, so isn't that what you want? | 01:39 |
Quintasan | I don't really know when to stop my friend | 01:39 |
Quintasan | say I do | 01:39 |
shadeslayer | ah | 01:40 |
Quintasan | for (int i = 0; i < 100; i++) { cout << *ptr+i; } | 01:40 |
Quintasan | and array is int arr = new int[50] | 01:40 |
Quintasan | Then I will get gibbrish in the output, won't I? | 01:40 |
shadeslayer | bbiab | 01:41 |
shadeslayer | yes | 01:41 |
shadeslayer | Quintasan: so, what I'd do is #define a macro called MAX_LENGTH and then use that everywhere | 01:44 |
shadeslayer | C is fugly in that regard | 01:44 |
Quintasan | that solution is still retarded because it kind of defeats the point of using dynamic allocation | 01:45 |
shadeslayer | OR | 01:45 |
Quintasan | wait | 01:45 |
Quintasan | I think I got something | 01:45 |
Quintasan | hmmm | 01:45 |
shadeslayer | use structs | 01:45 |
shadeslayer | how does that defeat dynamic allocation? | 01:45 |
shadeslayer | your array is still dynamically allocated | 01:45 |
shadeslayer | it's just the size that's constant | 01:45 |
Quintasan | how about you make the array +1 and make sure the last element is something like r#@WERWRQ and you parse for that? | 01:45 |
shadeslayer | sure, that'll work as well | 01:46 |
shadeslayer | but | 01:46 |
Quintasan | well the point with dynamic allocation is | 01:46 |
shadeslayer | what if the you inserted the same value in the array somewhere | 01:46 |
shadeslayer | like you have a array of length 50 with data | 01:46 |
Quintasan | if you need 50 elements then fucking allocate memory for 50 elements | 01:46 |
shadeslayer | and your terminating character is 55 | 01:46 |
Quintasan | don't allocated memory for 2131221321 elements and use 50 of them :P | 01:47 |
shadeslayer | and the second element in the array is also 55 | 01:47 |
shadeslayer | Quintasan: use a linked list ? :p | 01:47 |
shadeslayer | so much better for this case | 01:47 |
Quintasan | hmmm | 01:47 |
shadeslayer | you dynamically allocate each element in the list, you can traverse it easily, solves all your issues | 01:48 |
Quintasan | the exercise was to write a program that factorizes a number | 01:48 |
Quintasan | and my friend said they were supposed to store that shit in a array | 01:48 |
shadeslayer | a linked list behaves like an array? | 01:48 |
Quintasan | well, they were told to use a fucking array bro | 01:49 |
shadeslayer | that's just idiotic :/ | 01:49 |
Quintasan | like int arrrrrr[12312321]; | 01:49 |
Quintasan | I told him exactly them same thing | 01:49 |
Quintasan | well | 01:49 |
shadeslayer | :p | 01:49 |
shadeslayer | I mean sure, for some basic programming you can sue int array[65536] | 01:50 |
shadeslayer | but you can't keep using that for more complex problems | 01:50 |
Quintasan | if the array was supposed to be allocated as int arr[100] then it wouldn't be hard since you can just iterate over 100 elements to display the result | 01:50 |
shadeslayer | right | 01:50 |
Quintasan | but when you are supposed to use a function that returns and array a they want you to print that shit | 01:50 |
Quintasan | TIP: the exercise has actually two parts | 01:50 |
Quintasan | a) write that in Java | 01:50 |
Quintasan | b) write that in C++ | 01:51 |
shadeslayer | C++ | 01:51 |
shadeslayer | ftw | 01:51 |
shadeslayer | if you have to write it in C++ it's easier? | 01:51 |
Quintasan | I think his prof is kind of silly with that since in java you can do something stupid like .toString to print the whole shit | 01:51 |
shadeslayer | lol | 01:51 |
Quintasan | shadeslayer: Look, you don't have toString defined for you in C, do you? | 01:52 |
shadeslayer | nope | 01:52 |
Quintasan | That's it | 01:52 |
shadeslayer | but if you have to write it in C++ it's far easier | 01:52 |
shadeslayer | because C++ has better data types | 01:52 |
Quintasan | In Java you can just .toString and tell everyone to get the fuck out | 01:52 |
Quintasan | like what? | 01:52 |
Quintasan | how would you do that in cpp? | 01:52 |
shadeslayer | vectors | 01:52 |
shadeslayer | http://www.cplusplus.com/reference/vector/vector/ | 01:52 |
shadeslayer | dynamically sized arrays | 01:52 |
Quintasan | HOLY SHIT | 01:53 |
shadeslayer | that are resized as you push more elements | 01:53 |
Quintasan | I HAVE TO GO TO UNI IN 5 HOURS | 01:53 |
Quintasan | FML | 01:53 |
shadeslayer | haha | 01:53 |
Quintasan | NIGHT | 01:53 |
Quintasan | XD | 01:53 |
shadeslayer | heh night | 01:53 |
shadeslayer | Quintasan: srsly though | 01:53 |
shadeslayer | use vectors if you have to do it C++ | 01:54 |
Quintasan | mmkay | 01:54 |
Quintasan | will do | 01:54 |
shadeslayer | in C it's harder | 01:54 |
shadeslayer | but you can use LL's in C | 01:54 |
shadeslayer | bzr-tweet - Bazaar commit and push tweet plugin | 02:22 |
shadeslayer | because you want to tweet when using a revision control system :S | 02:22 |
shadeslayer | reminds me of terminal.app in OS X which allows you to tweet from the terminal but doesn't source ~/.bashrc when starting | 02:23 |
sreich | argh, stupid twitter hlol | 02:23 |
sreich | that's a good example of someone using something on the internet, and nobody caring about it | 02:24 |
shadeslayer | :) | 02:24 |
micahg | shadeslayer: why is it any different than KGB for IRC? | 02:25 |
shadeslayer | KGB? | 02:25 |
sreich | russian police, of course. | 02:25 |
shadeslayer | ah that thing which is replacing CIA | 02:25 |
sreich | duuuhh ;p | 02:25 |
sreich | is it doing anythign/goign anywhere? | 02:25 |
shadeslayer | idk | 02:25 |
shadeslayer | anyway | 02:25 |
shadeslayer | I don't view Twitter as a platform where you'd announce commit messages | 02:26 |
shadeslayer | new features in brief, sure | 02:26 |
sreich | i use notifico right now, it's awesome | 02:26 |
sreich | it's got a lovely site and it Just Works with my github project. | 02:26 |
shadeslayer | IRC is where developers hang out and it's usually useful to announce commit messages | 02:27 |
shadeslayer | Do developers hang out like we do on IRC? | 02:27 |
shadeslayer | erm | 02:27 |
shadeslayer | s/IRC/Twitter | 02:27 |
sreich | no idea | 02:27 |
sreich | i don't twat | 02:27 |
shadeslayer | me neither | 02:27 |
sreich | the only thing i've used it for though is notification of amd catalyst for windows | 02:27 |
sreich | since winderp doesn't have an update thing | 02:28 |
shadeslayer | Twitter is where I go to unwind, IRC is where I work | 02:28 |
sreich | or rather..it's got thousands of them ;p | 02:28 |
shadeslayer | hehehe | 02:28 |
mitya57 | apachelogger: hi, FYI one of your recent pkg-kde-tools uploads caused qt4 to FTBFS | 05:28 |
mitya57 | I've fixed it in https://bazaar.launchpad.net/~mitya57/kubuntu-packaging/qt-lp1094360/revision/356 | 05:29 |
mitya57 | But maybe there are more broken packages... | 05:29 |
soee | good morning | 07:22 |
shadeslayer | morning soee | 07:26 |
lordievader | Good morning | 08:33 |
=== apachelogger_ is now known as konvilogger | ||
=== mitya57_ is now known as mitya57 | ||
apachelogger | kde bug 314818 | 12:20 |
ubottu | KDE bug 314818 in ksysguard "Script error: Could not parse 'VmFlags: mr mw me ac'" [Normal,Resolved: fixed] http://bugs.kde.org/show_bug.cgi?id=314818 | 12:20 |
apachelogger | ScottK: curious, I hope you do not expect me to reply more than RTFM to the low-fat stuff? :S | 12:23 |
ScottK | no. | 12:23 |
apachelogger | k ^^ | 12:24 |
apachelogger | which reminds me | 12:24 |
* apachelogger creates card to review low-fat | 12:24 | |
ScottK | At they can get it from the correct distro. | 12:24 |
apachelogger | hm | 12:25 |
apachelogger | ScottK: actually forwarding to KDE may have been better | 12:25 |
ScottK | I'll leave that to you. | 12:26 |
apachelogger | <- too lazy | 12:26 |
konvilogger | pkgstriptranslations: no translation files, not creating tarball :/ | 12:30 |
konvilogger | ScottK: think it would cause problems if pkg-kde-tools had a dependency on python? | 12:40 |
konvilogger | ....either it needs to grow that dep or all our software that needs l10n does | 12:41 |
ScottK | I think it would be fine. I'd prefer python3, but not critical. | 12:47 |
konvilogger | ScottK: it's an upstream dep, so not much choice ^^ | 12:48 |
konvilogger | the l10n toolchain requires perl & sh & bash & python :S | 12:48 |
ScottK | K. | 12:48 |
=== mck182 is now known as mck182|lunch | ||
sheytan | apachelogger: ping | 13:05 |
konvilogger | sheytan: pong | 13:05 |
sheytan | konvilogger: you pinged me yesterday or something | 13:06 |
konvilogger | are you going to suggest your lightdm/ksplash themes on the ML? | 13:06 |
=== murthy_ is now known as murthy | ||
BluesKaj | Hiyas all | 13:07 |
murthy | hello everyone | 13:08 |
konvilogger | sheytan: ? | 13:11 |
kubotu | ::workspace-bugs:: [1156155] Script for menu option "Detailed Memory Information" fails to parse @ https://bugs.launchpad.net/bugs/1156155 (by jhoechtl) | 13:22 |
sheytan | konvilogger: i don't really know | 13:32 |
sheytan | i can | 13:33 |
sheytan | but as i wrote you in an email, can you send me the files again? :) | 13:33 |
konvilogger | lp:kubuntu-settings | 13:33 |
Riddell | 13:16 < stgraber> highvoltage, knome, Riddell, ScottK, zequence, phillw, (whoever else I forgot): Please make sure any slideshow change is in lp:ubiquity-slideshow-ubuntu by Wednesday 21:00 UTC. I'll review and upload on Thursday before UIF. | 13:35 |
Riddell | sheytan, apachelogger: same goes for boot splashes | 13:35 |
* apachelogger is too old for this | 13:36 | |
sheytan | Riddell: this wednesday? | 13:37 |
murthy | the last boot splash was fine one was fine, | 13:37 |
murthy | the last boot splash was fine | 13:37 |
murthy | sheytan: i thought the boot splash was finalised ? | 13:38 |
apachelogger | the splash is | 13:39 |
apachelogger | everything else is not | 13:39 |
sheytan | apachelogger: why it is not? | 13:39 |
sheytan | ldm is, splash for kde is | 13:39 |
sheytan | plymouth is | 13:39 |
apachelogger | lightdm is bugged | 13:39 |
murthy | apachelogger: the integration part ? | 13:39 |
apachelogger | splash has scaling diff with lightdm | 13:39 |
sheytan | apachelogger: what do you mean? | 13:39 |
apachelogger | both were not approved to be shipped | 13:39 |
sheytan | i send you the back ground in diff res | 13:40 |
apachelogger | as we have a standing policy to hold on to upstream we need to estabish agreement on whether to ship something else | 13:40 |
apachelogger | sheytan: it's all bugged | 13:40 |
sheytan | so it's pointless for me to send this to ML | 13:40 |
apachelogger | ? | 13:41 |
sheytan | we cannot put bugged stuff to the release | 13:41 |
apachelogger | bugs can be fixed | 13:41 |
sheytan | we have no time? | 13:41 |
apachelogger | I do not have time to fix the bugs now and then get bitched at by people for uploading artwork that was not approved | 13:42 |
apachelogger | hence why you need to spam the ML | 13:42 |
sheytan | ok, i will | 13:42 |
soee | is it possible to add some text at the end of beginning of each line in Kate ? | 14:04 |
Riddell | I'd use emacs macros for something like that | 14:04 |
=== mck182|lunch is now known as mck182 | ||
yofel_ | soee: if you're using vi input mode: ":%s/^/what_you_want_to_add/" | 14:08 |
yofel_ | for beginning, for end it's $, not ^ | 14:08 |
yofel_ | (simple regex) | 14:09 |
soee | yofel_, vi input mode in Kate> | 14:09 |
murthy | gambas support compiling to native exe? | 14:14 |
murthy | !ppa gambas | 14:21 |
ubottu | Sorry, I don't know anything about ppa gambas | 14:21 |
murthy | can this ppa be truested? ppa:nemh/gambas3 | 14:24 |
murthy | going out bbl | 14:29 |
=== murthy is now known as murthy_ | ||
Riddell | murthy_: no PPAs are considered trusted | 14:48 |
=== Adityab_ is now known as Adityab | ||
Quintasan | \o | 16:21 |
apachelogger | weeeh, I think my l10n crap is finally working | 17:01 |
apachelogger | hoorays | 17:01 |
apachelogger | no dpm though | 17:01 |
apachelogger | noooooooooooooooooooooooo :'( | 17:01 |
* apachelogger emits sighing | 17:03 | |
arokux1 | hi, any qt5 edgers here? I cannot find qtimageformats in the ppa. where is it? :( | 17:05 |
arokux1 | Mirv, hi, you seem to be responsible for building qt5? there were qtimageformats in other already deprecated ppas, but there isn't one in a qt5 proper. | 17:07 |
=== Adityab_ is now known as Adityab | ||
=== AbhiK is now known as AbhiK[-_-] | ||
=== AbhiK[-_-] is now known as AbhiK | ||
jussi | wow, quiet tonight... | 19:15 |
=== Adityab_ is now known as Adityab | ||
kubotu | ::workspace-bugs:: [1156155] Script for menu option "Detailed Memory Information" fails to parse @ https://bugs.launchpad.net/bugs/1156155 (by jhoechtl) | 20:51 |
ScottK | Riddell: tech board is discussing the new release proposal in #ubuntu-meeting if you're around ... | 21:13 |
Quintasan | argh | 21:43 |
Quintasan | ScottK: So we're rollling release? | 21:43 |
ScottK | No. | 21:44 |
ScottK | Mark's modified version where we just shorten the support window. | 21:44 |
Quintasan | ScottK: I imagined you saying that in a grave voice. That sounded really grave. | 21:44 |
ScottK | It's going OK so far. | 21:45 |
Quintasan | Hmm, so support window for non-LTS releases is 9 months now. | 21:45 |
ScottK | Yes. | 21:46 |
ScottK | But we'll also support upgrades of LTS -> Current so you aren't stuck on LTS. | 21:46 |
Quintasan | lol | 21:55 |
Quintasan | wtf | 21:55 |
=== Adityab_ is now known as Adityab | ||
Riddell | ScottK: so a happy ending? | 22:56 |
ScottK | Riddell: Reasonably. They didn't get through the whole thing. What was decided is 9 months of support for regular releases and a standing symlink to the development series so people who want to stay on the development series can. | 22:57 |
ScottK | Also it's a "regular release", an "LTS release", or the "development series". No "rolling release". Concluded that's an oxymoron. | 22:58 |
Riddell | I'm glad that 'interim' term didn't stick | 23:03 |
* ScottK too. | 23:03 | |
* Quintasan had to look up "interim" in a dictionary | 23:15 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!