|
Shaggar posted:the code clarity rules are basically: "dont do all those stupid loving obfuscation hacks they taught you in that 'functional'/p-language" of the 31 items, one is tenuously related to functional programming and the other 30 are unrelated. grats
|
# ? Aug 8, 2012 18:05 |
|
|
# ? May 8, 2024 06:49 |
|
pretty much all of them have to do with verifiability of things at compile time and avoiding operations the could conceivably block or take longer than expected. good luck not doing any dynamic allocation in java!
|
# ? Aug 8, 2012 18:07 |
|
shaggar probably didn't read the code rules
|
# ? Aug 8, 2012 18:08 |
|
I didn't either
|
# ? Aug 8, 2012 18:09 |
|
i need explicit standards bc i have none of my own
|
# ? Aug 8, 2012 18:15 |
|
Star War Sex Parrot posted:
|
# ? Aug 8, 2012 18:18 |
|
PrBacterio posted:
bbbbbbbbbut it might be ******unclear******* to the person we hire to try to do your job for half the price in a couple years! Please document your code well so that we may easily outsource it after youve done all the real work
|
# ? Aug 8, 2012 18:20 |
|
Otto Skorzeny posted:of the 31 items, one is tenuously related to functional programming and the other 30 are unrelated. grats its msotly about getting rid of dumb poo poo where the flow of the code is not instantly obvious. those are things you just cant do in java b/c the creators were smart enough to leave useless obfuscations out. the type of obfuscations you pick up from bad-habit-forming languages like p-languages or "functional" languages. they're obviously programming in c so while it may not have the exact same concepts as those languages, it gives the user enough rope to hang themselves.
|
# ? Aug 8, 2012 18:20 |
|
good use of the term "mission critical" in this doc
|
# ? Aug 8, 2012 18:20 |
|
PrBacterio posted:Have fun adding a bunch of pointless new checks and hakcs, each time when updating/changing compilers, and then removing them again for the very next version; -- or alternatively -- using a huge steaming pile of #ifdef COMPILER_VERSIONs, because lots of times compilers yeah we have one loving shot to get this to another goddamn planet, let's switch it up to gcc 3.4.3 because we really need to swap the compiler 8 or 9 times instead of just sticking to ONE that works
|
# ? Aug 8, 2012 18:24 |
|
bbb.b.bbbb.butt gcc 3.2.3 adds more pre-processing for me to abuse!!
|
# ? Aug 8, 2012 18:25 |
|
graph posted:lol if you go to college to learn how to program
|
# ? Aug 8, 2012 18:26 |
|
Jonny 290 posted:bbbbbbbbbut it might be ******unclear******* to the person we hire to try to do your job for half the price in a couple years! Please document your code well so that we may easily outsource it after youve done all the real work it might be unclear to you when you look at it in a month, that's why "Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" - brian kernighan
|
# ? Aug 8, 2012 18:29 |
|
PrBacterio posted:Have fun adding a bunch of pointless new checks and hakcs, each time when updating/changing compilers, and then removing them again for the very next version; -- or alternatively -- using a huge steaming pile of #ifdef COMPILER_VERSIONs, because lots of times compilers and their various versions aren't even in agreement over what constructs they should complain about or if they should do so when they're present/missing. Oh and also lots of superfluous brackets because apparently actually using the language's precedence rules is for scrubs. don't worry, #ifdef COMPILER_VERSIONs aren't allowed either
|
# ? Aug 8, 2012 18:32 |
|
lol look at all you hating on the loving jpl, go inhale some cheetos nerds
|
# ? Aug 8, 2012 18:55 |
|
Mr Dog posted:If you need explicit coding standards then your development team consists of either idiots or prima donnas, congrats that's a really dumb thing to say
|
# ? Aug 8, 2012 19:07 |
|
tef posted:but yeah, assuming you don't have to do database stuff, user authentication, management,
|
# ? Aug 8, 2012 19:07 |
|
velocity is better for templating
|
# ? Aug 8, 2012 19:09 |
|
PrBacterio posted:Have fun adding a bunch of pointless new checks and hakcs, each time when updating/changing compilers, and then removing them again for the very next version; -- or alternatively -- using a huge steaming pile of #ifdef COMPILER_VERSIONs, because lots of times compilers and their various versions aren't even in agreement over what constructs they should complain about or if they should do so when they're present/missing. Oh and also lots of superfluous brackets because apparently actually using the language's precedence rules is for scrubs. lol if you think they are using anything remotely close to the latest version
|
# ? Aug 8, 2012 19:10 |
|
PrBacterio posted:Have fun adding a bunch of pointless new checks and hakcs, each time when updating/changing compilers, and then removing them again for the very next version; -- or alternatively -- using a huge steaming pile of #ifdef COMPILER_VERSIONs, because lots of times compilers and their various versions aren't even in agreement over what constructs they should complain about or if they should do so when they're present/missing. Oh and also lots of superfluous brackets because apparently actually using the language's precedence rules is for scrubs. When you have one chance to do a thing that costs billions of dollars you better loving make sure everything checks out. also, trex eaterofcadrs posted:lol look at all you hating on the loving jpl, go inhale some cheetos nerds
|
# ? Aug 8, 2012 19:10 |
|
vapid cutlery posted:lol if you think they are using anything remotely close to the latest version if they're just doing ansi c it doesn't matter
|
# ? Aug 8, 2012 19:15 |
|
trex eaterofcadrs posted:lol look at all you hating on the loving jpl, go inhale some cheetos nerds
|
# ? Aug 8, 2012 19:15 |
|
PrBacterio posted:Have fun adding a bunch of pointless new checks and hakcs, each time when updating/changing compilers, and then removing them again for the very next version; -- or alternatively -- using a huge steaming pile of #ifdef COMPILER_VERSIONs, because lots of times compilers and their various versions aren't even in agreement over what constructs they should complain about or if they should do so when they're present/missing. Oh and also lots of superfluous brackets because apparently actually using the language's precedence rules is for scrubs. I know Jawn already told you why you're a loving idiot, but let me just add that you're mentally damaged if you think chaning compilers used for an already functioning project is a reasonable thing to do.
|
# ? Aug 8, 2012 19:20 |
|
Cocoa Crispies posted:if they're just doing ansi c it doesn't matter We need to upgrade to gcc 4.7 and also patch in autovectorization support for our 16-bit microcontroller build target
|
# ? Aug 8, 2012 19:21 |
|
quote:If a function (say my function is AddTwoNumbers(x,y) - which adds X + Y and returns the value) sends something back to you. You must check that number before doing anything with it.
|
# ? Aug 8, 2012 19:33 |
|
what's wrong with that?
|
# ? Aug 8, 2012 19:51 |
|
Nomnom Cookie posted:We need to upgrade to gcc 4.7 and also patch in autovectorization support for our 16-bit microcontroller build target it's actually a 32-bit powerpc just like my olde ibook
|
# ? Aug 8, 2012 19:51 |
|
no wonder its so slow and expensive
|
# ? Aug 8, 2012 19:52 |
|
vapid cutlery posted:what's wrong with that? heh remember when php tried to check for arithmetic overflow using the same types they were adding and then switched to floating point instead
|
# ? Aug 8, 2012 19:55 |
|
no one here has any experience with anything close to what jpl does except maybe jawn. ok cya
|
# ? Aug 8, 2012 19:56 |
|
in the context they are using it that actually makes perfect sense
|
# ? Aug 8, 2012 19:57 |
|
vapid cutlery posted:what's wrong with that? 2) if(i > INT_MAX) Gazpacho fucked around with this message at 20:04 on Aug 8, 2012 |
# ? Aug 8, 2012 20:01 |
|
vapid cutlery posted:no one here has any experience with anything close to what jpl does except maybe jawn. ok cya
|
# ? Aug 8, 2012 20:02 |
|
most of the c in curiosity is written by python programs: http://programmers.stackexchange.com/a/159687Gazpacho posted:i know crazy poo poo happens in space but if you cant even trust your ALU then you better shield that poo poo until you can they do but it's still an issue
|
# ? Aug 8, 2012 20:07 |
|
just use a transputer im p sure theyre approved for space
|
# ? Aug 8, 2012 20:07 |
|
just use a thin client
|
# ? Aug 8, 2012 20:09 |
|
if you want to watch retards argue pedantics about curiosity here is the link for you: http://news.ycombinator.com/item?id=4348448
|
# ? Aug 8, 2012 20:09 |
|
it's cool how tihs always happens. some company or govt body that has been doing things successfully for over 50 years shares some insight into how they do things, and goons come out of everywhere to tell them they're wrong
|
# ? Aug 8, 2012 20:14 |
|
trex eaterofcadrs posted:lol look at all you hating on the loving jpl, go inhale some cheetos nerds
|
# ? Aug 8, 2012 20:16 |
|
|
# ? May 8, 2024 06:49 |
|
its ok i know more about space programming and everything they've experienced in the past trust me i got this "Fuckin jpl nerds dont do it that way"
|
# ? Aug 8, 2012 20:17 |