Elos posted:

gonna have to write some java for a course soon

gucci void main posted:

i have an interview thursday

gucci void main posted:

p.s., i'm really sick of the term "hit the ground running" cause it's the most over-loving-used phrase. post your most clichéd IT job phrases here

volkadav posted:

I thought I hated php, then I got a project at work that has lead to crawling up its rear end with gdb.

gently caress YOU, ZEND!!



At least there's PHP's wonderful documentation to fall back on.

Paracetamol Boy posted:

does anyone here actually enjoy working with libboost for the sake of working with libboost

rotor posted:

everyone needs to learn more perl imho

Paracetamol Boy posted:

boost is useful but there is this guy who uses boost for stuff that he can code natively in fewer lines than it takes to code the thing using boost

i do not understand this

Paracetamol Boy posted:

boost PO instead of just using main args?
crazytalk

boost docs posted:

Introduction

The program_options library allows program developers to obtain program options, that is (name, value) pairs from the user, via conventional methods such as command line and config file.

Why would you use such a library, and why is it better than parsing your command line by straightforward hand-written code?

It's easier. The syntax for declaring options is simple, and the library itself is small. Things like conversion of option values to desired type and storing into program variables are handled automatically.

Error reporting is better. All the problems with the command line are reported, while hand-written code can just misparse the input. In addition, the usage message can be automatically generated, to avoid falling out of sync with the real list of options.

Options can be read from anywhere. Sooner or later the command line will be not enough for your users, and you'll want config files or maybe even environment variables. These can be added without significant effort on your part.

shrughes posted:

Maybe you should go cry about it then. I'm so sorry there's people with more money than you and people making more money than you that make you jealous.

Star War Sex Parrot posted:

what's a technologist

am I one?

Tiny Bug Child posted:

you're as retarded as mr. homework help; the original instructions weren't really unclear

Shaggar posted:

its mac only so theres no reason to ever use it.

Tiny Bug Child posted:

this except the literal opposite

Otto Skorzeny posted:

also ocaml is a pretty darn good language for writing a compiler in

Wheany posted:

How to write a multithreaded application:

1) Just make your application single-threaded
2) Copy this bat file as many times as you have processors, with different parameters in each file, duh:

DOS code:

yourapplication.exe inputfile1 outputfile1
yourapplication.exe inputfile2 outputfile2
yourapplication.exe inputfile3 outputfile3
yourapplication.exe inputfile4 outputfile4

3) Then copy and run this bat:

DOS code:

start batch1.bat
start batch2.bat
start batch3.bat
start batch4.bat

4) profit

Tiny Bug Child posted:

php is like jet fighters. fast, powerful, can do p much anything, sometimes crashes b/c of pilot error

Shaggar posted:

dont bother going from one p-lang to another. they're all crap.

JawnV6 posted:

perl's the shortest distance between "i know a computer can do this" and it being done

"shortest" doesn't imply "best"

Tiny Bug Child posted:

PHP

EVGA Longoria posted:

driving an open road with the top down on a beautiful day, letting all you worries evaporate

ZYNGA STOCK CRASHER posted:

ban 4 anime n aspergers

Cocoa Crispies posted:

Shaggar posted:

the only time you can have non-blocking io is when you dont care what the result of the io operation is. this means it doesnt matter what any of the rest of your code does.