logs archiveBotHelp.net / Freenode / #2f30 / 2015 / August / 4 / 1
dca7
sup guys
kori
dca7: didn't you own the nick dcat here
dca7
nope
kori
weird
stateless
morning
FRIGN
yo stateless
there?
atmc
FRIGN: do you have a nice snippet for notation table in latex?
FRIGN
I wrote one recently
atmc
gieve
FRIGN
atmc: http://www.mi.uni-koeln.de/AG-Kunoth/file/manual/Lehre/SS15/Num1/num1_2015(1).pdf, p.118
just let me know if you need something like this
atmc
that looks promising
good old kronecker delta
openfbtd
I am very disappointed that colors is not called colours
(Action) squints at sin
Also the makefile doesn't build hext2col
hex2col*
Not a problem obviously tho
FRIGN
atmc: something like this?
it's actually not too complex though
stateless
openfbtd, yeah did not bother building it
z3bra wrote hex2col.c :P
z3bra
surprisingly though
:P
should the makefile compile hex2col too?
stateless
no i don't think so
it is just a tool
z3bra
yeah that's what I though too
maybe add a "#!/usr/bin/tcc -run" at the top ;)
FRIGN
stateless: yo, quick question
I'm currently auditing sort(1)
and when the -c or -C flags are given, only one input file is allowed
(by Posix)
stateless
ok
FRIGN
however, it's possible to do that with multiple files as well
currently, check() does an exit(), which is not clean in terms of fshut and so on
so I though: Hey, why not just fu*k Posix and allow multiple files
stateless
right so
FRIGN
for instance, if you wanted to check sort1.txt sort2.txt sort3.txt
or a big list
stateless
if i did sort -c 1.c 2.c it would return 0 only if both were sorted?
FRIGN
it would be:
sort -c 1.c 2.c
yes, only if both would be
stateless
ok
I think it makes sense tbh
FRIGN
yeah
no idea why posix is so strict on it
another thing:
posix says it should return 1 if both the u-flag and c-flag is given
Under the -c option, the file was not ordered as specified, or if the -c and -u options were both specified, two input lines were found with equal keys.
and two input lines found with equal keys
stateless
yes
for -u from openbsd sort: "If used with -C or -c, sort also checks that there are no lines with duplicate keys."
FRIGN
okay
does our sort do this?
stateless
haven't tested this
definitely worth a try
I am trying to understand why -c is fixed to 1 arg
the rationale
retard
https://www.youtube.com/watch?v=v25QjMYeZVk this woman is making me sexist
FRIGN
stateless: hmm
openfbtd
stateless, my pkgbuild just calls gcc -o hex2col hex2col.c :D
FRIGN
stateless: ha, founda bug! ^^
it would return 1 if fshut failed instead of t
stateless
FRIGN, aha one sec, I will share my findings
openfbtd
So, as I've said, not a problem :)
FRIGN
2
stateless
ok so
FRIGN, I tested sort -c on linux, bsd, irix and solaris
the first three bail out if it has more than one arg
solaris works as you say
;)
fu*k posix
FRIGN
yeah
fu*k it
okay, what about -u with duplicate key?
retard
right in the pu**y?
stateless
FRIGN, we need to support that
FRIGN
yeah
stateless
as POSIX says
yeah returning 2 is fine if sth else fails internally
FRIGN
stateless: let me check check()
stateless
lol ok
retard, https://www.youtube.com/watch?v=mOv62lBdlXU
FRIGN
stateless: ah we do it
if (uflag > linecmp(...))
haha, what a nice hack ^^
stateless
haha nice
FRIGN
also, I add char *fname to check()
retard
internet kind stuff
FRIGN
so we print the filename as well
retard
happy and blinking
this guy is gr8
stateless
retard, I would do the math but I am too excited to think right now
hahaha
retard
packets per second
THIS IS THE CASH
jesus fu*k wh..
« prev 1 2 3 4 next »