pugs.blogs.com | pugscode.org | pugs.kwiki.org | paste: sial.org/pbot/perl6 | <stevan> Moose... it's the new Camel ":P | .pmc == PPI source filters!
Set by Alias_ on 16 March 2006.
00:00 ayrnieu left, ayrnieu joined, ayrnieu left 00:01 ayrnieu joined
ayrnieu grumbles. 00:01
00:08 pdcawley joined 00:09 pdcawley_ joined 00:20 Quell joined
wolverian Juerd, hey, nice colours on juerd.nl :) 00:21
Juerd wolverian: It's random, so cache them while you can ;) 00:22
wolverian yeah, I noticed :) 00:23
Juerd It's some perl module that generates them. Most of the time, it's nice. 00:25
I haven't figured out how to calculate which one of <white black> will contrast most, though.
jisom convert to grayscale, measure the difference, if not enough, recalculate?
Juerd jisom: I don't know how to convert to grayscale properly. 00:26
The mean of R, G and B, certainly isn't useful.
jisom I know swing has one in it's source....but it might be sufficient to try 00:27
wolverian Juerd, hold a sec, I'll get you the coefficients
FurnaceBoy Juerd, you can also add 0x80,0x80,0x80 to get a highly contrasting colour. 00:32
add and modulo
TimToady won't that turn gray into gray? 00:33
FurnaceBoy no, it would turn 0x80,0x80,0x80 into white :-)
sorry, into black
TimToady ah, gotcha.
FurnaceBoy but 0x7f,0x7f,0x7f into white 00:34
particle_ sees a red door
FurnaceBoy it's sorta handy for overlaying stuff.
TimToady don't eat the red door.
FurnaceBoy where you have a continuously changing background like an image
so cannot pick a single colour to contrast
Juerd FurnaceBoy: No, adding 0x80 xx 3 doesn't help on bright colours... 00:35
TimToady Seems like xor with 0x80,0x80,0x80 does the same thing...
Juerd FurnaceBoy: Oh, modulo.. Hmmm...
FurnaceBoy TimToady, no
hmm
yes
:-)
Juerd FurnaceBoy: I guess it would create something contrasting, but I'd like to stick to black and white. 00:36
FurnaceBoy yes
it's really only useful for image-like backgrounds
jisom a % 0x80 => a & 0x7f
wolverian Juerd, Color::Scheme has a convenient looking ->distance() method, btw. anyway, here are the coefficients for the channels if you want to calculate the contrast for a human eye: 0.30 0.59 0.11 (RGB). then calculate the distance as if the channels were dimensions, normalising if you want.
FurnaceBoy that's not actually based on the eye; those are the traditional NTSC coefficients 00:37
wolverian oh, sorry.
FurnaceBoy well, they're based on the eye to the extent the 195x NTSC coeffs are :-)
mostly still used
wolverian do you have better ones?
FurnaceBoy no, was just nitpicking. ;_)
wolverian ok :)
Juerd wolverian: I lack math skills to understand that, though. What's a coefficient, and everything from "calculate the distance" I understand in English, yet I don't know what it actually means :)
FurnaceBoy the NTSC are still commonly used
Istr a paper on perceptual neutral density ... hmm. 00:38
wolverian Juerd, each value there is multiplied against the two colours' difference for that channel. i.e. 0.3 * (col1.r - col2.r) etc.
Juerd wolverian: But I only have one colour, the background colour.
wolverian oh, then I misunderstood what you wanted. :) 00:39
FurnaceBoy well,
those coeffs still give you a useful grey conversion
g = .30r + .59g + .11b
Juerd Given a certain background colour, I want to know if white or black is the better foreground colour.
FurnaceBoy note (.30+.59+.11) = 1.0
wolverian Juerd, then you _do_ have two colours, or three, to be exact. 00:40
FurnaceBoy yes, you can grey-ise as above
then check whether it's >.5 or <.5
Juerd wolverian: Really?
wolverian Juerd, white, black, and your bg colour.
Juerd FurnaceBoy: Ahh. I'll try that.
wolverian: Hmm.
wolverian FurnaceBoy's method should work fine here.
FurnaceBoy fwiw, I believe Photoshop's RGB->Grey Scale conversion still uses those exact coefficients. 00:41
absent colour management settings.
wolverian you don't need to calculate the real distance, only compare distances, and that works fine with manhattan distance
(too many 'distance's there..)
FurnaceBoy, er, isn't NTSC YUV? 00:42
FurnaceBoy, or do you mean those coefficients are what it comes to after translating to RGB? sorry, slow tonight..
Arathorn NTSC's only YUV if you happen to digitize it into chrominance & luminance 00:43
Arathorn promptly stops talking, given he can't remember how the colourburst is encoded in PAL, let alone Never The Same Color twice
FurnaceBoy "The coefficients 0.299, 0.587 and 0.114 properly computed luminance for monitors having phosphors that were contemporary at the introduction of NTSC television in 1953, however, these coefficients do not accurately compute luminance for contemporary monitors." 00:44
wolverian FurnaceBoy, thanks.
FurnaceBoy I would concur with that last remark, those coeffs aren't quite right for usual screens
wolverian well, screens differ hugely in colour reproduction anyway
FurnaceBoy yep.
and Juerd only needs a "close enough for govt work" answer :-)
wolverian LCDs have really bad curves
wolverian hates his laptop's "black", which is more like gray 00:45
FurnaceBoy this guy is a colour theory master www.poynton.com/
wolverian FurnaceBoy++
Juerd FurnaceBoy: This works quite well. I used a threshold of 0x90 instead of 0x80, though.
FurnaceBoy yeah, that's probably exactly the result of the gamma shift since 1953 :-) 00:46
Juerd wolverian: Almost all TFT black is gray, because TFT's natural colour is white.
wolverian yeah. OLED please. :)
FurnaceBoy yeah. subtractive
Juerd wolverian: The pixels don't manage to fully block that.
FurnaceBoy but this Samsung is mightly black...
Juerd FurnaceBoy: And probably glossy too, then.
FurnaceBoy except it still suffers a lot at the dark end of the range
playing MPEG for instance
wolverian Juerd, hm, is juerd.nl using the new code now? I'm getting somewhat non-contrasty results for the date title on the frontpage 00:47
Juerd I hate glossy screens.
FurnaceBoy no, it's fairly matte
just a good 1:700 or more
Juerd wolverian: Yes, it is.
ayrnieu black looks quite good on this Apple Cinema 20" -- but yes, glossy.
Juerd wolverian: Did you get white?
wolverian I got white text on a very light blue
let me check the colours
Juerd I'll get it back to 0x80 then
See /css.plp, the comments at the top 00:48
I need to base things differently for the code blocks
00:48 Arathorn is now known as Aragone
wolverian I got (128, 255, 247) for the bg of the <h2> and white as the text colour 00:49
(that's 80fff7)
Juerd I was using the wrong colours for the background :) 00:51
The calculation was based on the pure colour, not the lighter tint
wolverian ah. :)
ow, got a bad one again 00:52
Juerd Yea, I'm lost in my single letter variables, and meaningless array indices. 00:53
wolverian Color::Scheme looks really nice. I'll try this on my css files.. :)
Juerd It should be okay now 00:54
wolverian: Beware... you'll like it, your visitors will like it, and it will cost you more time than you now think it does.
wolverian seems to be
Juerd, oh, I don't have any visitors.
Juerd tnx.nl/4603WGFV # horrible code 00:55
wolverian eww :)
Juerd Worse is that it leads to things like 00:56
background: <:= $c[2][0] :>;
color: <:= $c[2][4] :>;
wolverian egh, my $b = ...$b[0]...$b[1]...; # wow that is confusing :)
Juerd Yea. 00:57
And don't make the mistake of thinking 'c' stands for colour. That's purely coincidental.
I've written more than enough crappy code in my life to know what is and what is not maintainable. Still, for private site things, I *like* messing around with crappy code. 00:59
wolverian procrastinating..
Juerd What's that?
wolverian putting off something by distracting yourself with something else
Juerd Ah, I did that all day without knowing there was a word for it :) 01:00
wolverian :)
Juerd Spent half a day rewiring parts of my car. Should have done taxes.
ayrnieu procrastination also refers to a kind of clever task management.
Juerd I'm going to bed now
Thanks for helping me with the colour issue 01:01
And thanks for delaying my sleep with that ;)
Juerd --zzz & # .zZ
wolverian night :)
jisom finally I got it working....in a mostly correct way but nothing more than a "floating point" error 01:02
01:04 mako132_ joined 01:12 ajani joined 01:14 ajani is now known as ajani_ 01:15 ajani_ is now known as ajani
Juerd I'm still awake. Damn you, internet! :) 01:16
Juerd afk now
wolverian pushes Juerd to the bed
01:17 justatheory joined 02:05 p5evalbot joined, GabrielVieira joined 02:52 buu joined 02:59 xern joined 03:12 amnesiac joined 03:21 buu joined 03:45 Khisanth joined 04:03 KingDiamond joined 04:40 stevan_ joined 05:08 elmex_ joined 05:11 stevan joined 05:31 vel joined
svnbot6 r9671 | Darren_Duncan++ | r3250@darren-duncans-power-mac-g4: darrenduncan | 2006-03-20 12:58:49 -0800 05:33
r9671 | Darren_Duncan++ | ext/Rosetta/ : updated the class complement of Rosetta.pm
r9672 | Darren_Duncan++ | r3253@darren-duncans-power-mac-g4: darrenduncan | 2006-03-20 15:18:27 -0800
r9672 | Darren_Duncan++ | ext/Rosetta/ : completed initial Rosetta Shell, which executes
r9673 | Darren_Duncan++ | r3256@darren-duncans-power-mac-g4: darrenduncan | 2006-03-20 16:36:33 -0800
r9673 | Darren_Duncan++ | ext/Rosetta/ : final smaller updates synchronizing with perl 5 version CPAN release v0.722.0
dduncan well, the server woke up, thankfully
05:36 vel joined 05:40 mj41__ joined 05:46 Kattana joined 05:49 nirgle joined 05:56 Quell joined
svnbot6 r9674 | Darren_Duncan++ | r3262@darren-duncans-power-mac-g4: darrenduncan | 2006-03-20 22:12:30 -0800 06:15
r9674 | Darren_Duncan++ | ext/Rosetta/ : following today's release on CPAN of the Perl 5 flavor, incremented all major version numbers ; also, a few pod fixes
06:16 amnesiac joined 06:35 GeJ joined 07:01 xern joined 07:04 FurnaceBoy_ joined 07:10 iblechbot joined, FurnaceBoy_ left 07:24 dduncan left, drrho joined 07:27 stevan joined 07:32 Quell joined 07:36 Quell joined 07:37 ghenry joined 07:41 lisppaste3 joined 07:43 nothingmuch joined
nothingmuch morning 07:47
Supaplex zzZzzz 07:50
nothingmuch ingy: ping 07:58
07:59 beppu_ joined 08:06 marmic joined
gaal ingy: ping 08:31
Supaplex ZZZzzz....ong...*snort* 08:34
08:40 wilx joined 08:42 kane_ joined 08:50 Chiicco24 joined, stennie joined, Chiicco24 left 09:15 nnunley joined 09:50 nnunley_ joined 09:51 KingDiamond joined 10:02 penk joined 10:07 kattana_ joined 10:20 stevan joined 10:22 nnunley_ is now known as nnunley 10:44 xinming joined 10:57 pjcj joined 10:58 nivrrex joined 10:59 nivrrex left 11:00 szbalint joined 11:05 chris2 joined
ingy gaal: yes? 11:28
nothingmuch ingy ping too
can i have that script you use to make a symlinked @INC entry to a dist like layout?
ingy nothingmuch: elk?
nothingmuch ingy: møøse 11:29
ingy nothingmuch: sure, looking for it... 11:30
nothingmuch: svn.kwiki.org/kwiki/bin/make-lib-tree.pl 11:31
nothingmuch: put it in your path and then just tell it about various sources 11:32
it creates ./lib/
nothingmuch thanks
ingy and remembers all old sources in ./lib/.sources/
and remembers all old sources in ./lib/.sources
rather
nothingmuch møøse 11:33
ingy so when you run it with no arguments, it refreshes
elk
nothingmuch yay
btw, what's your current email?
ingy it doesn't recurse though
make-lib-tree.pl ~/src/ingy/* ~/src/pugs/perl5/* 11:34
[email@hidden.address]
nothingmuch why not [email@hidden.address]
ingy laziness
nothingmuch i'll give you ingy@møø.se if i manage to buy that domain 11:35
it's not allowed
but i think i sort of managed
ingy ? 11:36
not allowed?
besides it would be [email@hidden.address] :p 11:37
11:37 renato joined
nothingmuch ingy: .se don't like ø 11:37
make [email@hidden.address] an alias please 11:38
i will never manage to remember anything else
osfameron nothingmuch: have you got moo.se ? 11:39
nothingmuch osfameron: no 11:40
it's just parked =(
ingy how about mooooo.se? 11:42
nothingmuch no, that's lame
ingy or m00.se
nothingmuch i wouldn't mind that if i don't get møø.se
ingy ø_0 11:43
gaal ingy: hi. quick yaml question 11:45
I want heredoc-style quoting, like |
but want to avoid the need for indentation in that quoted node
can I?
11:46 ruoso joined
ingy gaal: no 11:46
gaal too bad :/
I understand why it wouldn't be
ingy how would you know the end?
gaal |<<"END" :-P 11:47
ingy would require heredoc
yep
what's the use case?
gaal I wanted to make yaml the encoding for this: search.cpan.org/~gaal/Template-Patc.../metapatch 11:48
the templates need to be trivially human-editable
ingy yaml is trivially human-readable, but not always trivially human edit-able 11:49
gaal yes indeedy
I appreciate the tradeoff, it just leans the wrong way for my current application. oh well :)
nothingmuch couldn't '-|' be extended into '- 11:50
'-| __marker__'
<non indented text here
__marker__ 11:51
?
ingy the cool thing about the verbatim block, is that you can trivally embed any yaml in yaml
yaml is .il technology :p
nothingmuch oops, didn't notice backlog
gaal bad nothingmuch
nothingmuch sorry, i skipped just that line
i swear
gaal nothingmuch: i wonder, is oo.se maybe free? :) 11:52
isn't.
nothingmuch checked =) 11:53
i wouldn't have minded m.oo.se
it's ver del.icio.us
i mean ver.y
or v.er.y
gaal e.lk (sri lanka) 11:54
ingy :D
i.lk
ingy goes back to Chinese lesson 11:55
11:57 mako132_ joined
svnbot6 r9675 | broquaint++ | * Added PadWalker 1.0 to Makefile.PL. 11:59
ruoso is porting lrep-compiler to PCR 12:07
Juerd $foo[7] = "bah"; 12:10
Wrong channel.
nothingmuch ruoso: PCR?
Pugs::Compile::Rules?
gaal Juerd: yes, for it to be right for this channel you'd have to have said @foo[7] = "bah"; :-) 12:14
Juerd gaal: Oh? $foo[7] = "bah"; works well in Perl 6. 12:15
It doesn't touch @foo, but it does work.
In fact, it was a PHP example, making $foo[7] the direct translation, in Perl 6. 12:16
As PHP has only array (hash, really) *references*
ruoso nothingmuch, yes
Aragone $foo[7] in perl6 makes $foo an arrayref, then?
ruoso Aragone, yes 12:17
gaal takes $foo to be an arrayref, rather 12:19
?eval my $foo = "scalar"; $foo[7] = "oops"; $foo.perl
anyway, that's "*** Can't modify constant item: VUndef" 12:21
which is probably not the best error message possible here :/
gaal woos evalbot back
ruoso is recompiling the new Perl6.p6 that already uses PCR 12:22
12:24 nirgle left
ruoso wonders if fglock renamed some capture nodes 12:27
Juerd gaal: Well, $foo is nicely autovififithingied if it's undef :)
gaal Juerd: ACK
Juerd That single feature that's keeping me away from Ruby. 12:28
12:58 pmurias joined
pmurias hi roso 12:58
svnbot6 r9676 | pmurias++ | the hybrid wird not-realy working port to the PCR
ruoso pmurias, I was wainting for you
pmurias nice of you 12:59
ruoso pmurias, :) so... is this commit *the* commit?
pmurias yes 13:00
ruoso does it uses PCR from CPAN or from pX? 13:01
pmurias tested only on the pX one, you have to send PERL5LIB to run it
ruoso ah... ok... 13:02
I'll change the Makefile to reflect that
13:05 fglock joined
ruoso pmurias, hmmm.... not working... 13:05
pmurias, oh... ok... saw the commit log now 13:06
pmurias hi fglock
the part which I could get right yesterday was the old rules and PCR rules interop 13:07
s/could/couldn't/
ruoso pmurias, that's the hard part
pmurias, :)
13:07 Limbic_Region joined
pmurias ruoso: it's mostly a matter of determining how the rule API changed 13:08
ruoso pmurias, that's exactly the question I was about to make to fglock 13:09
fglock, ? 13:10
Not an ARRAY reference at ...Pugs/Runtime/Rule.pm line 94 13:11
13:11 iblechbot joined
ruoso this was the error I was getting in the try I was making before your commit 13:11
fglock hi! - I'm trying to commit the $0,$1 implementation - but got to merge first :(
ruoso fglock, is the "Not an ARRAY" error related to that? 13:12
fglock ruoso: looking... 13:13
ruoso: that's a problem with the match{state}, which is an internal variable - it should never happen 13:14
ruoso fglock, only when you mix old with new code... :) 13:15
fglock, how the state should looks like...
fglock, so I can wrap it...
fglock ruoso: state is an array with [ number, state ] 13:16
Aragone (btw, you do know that the concat function in Pugs::Runtime::Rule2 in the released PCR 0.01 on cpan is mangled?) 13:18
svnbot6 r9677 | fglock++ | pX/../PCR - $0, $1 13:19
fglock Aragone: looking... 13:20
Aragone: looks ok - search.cpan.org/src/FGLOCK/Pugs-Com...e/Rule2.pm 13:21
but this file is gone in the new version
work &
Aragone it tries to recurse to Pugs::Emitter::Rule::Perl5::concat()
though
(it's fixed in the new version)
rather than itself 13:22
13:22 kanru joined
ruoso fglock, I see that 'push @list, rule' now pushes a string instead of a sub... 13:23
in PCR
fglock, I'm a little bit confused.. 13:25
fglock ruoso: the list is processed into method calls in the end of Pugs::Grammar::Rule 13:28
ruoso fglock, ah ok
fglock, this should be changed, shouldn't it? 13:29
ruoso getting back to Perl6::Bible to see how the syntax should looks like 13:30
svnbot6 r9679 | pmurias++ | $grammar_namespace now passed to the PCR emitter 13:31
fglock ruoso: there are 2 kinds of rules in PCR: methods and objects. @list expects a list of objects - so we need to curry the methods into rule-objects. I don't know if this is correct 13:32
ruoso fglock, so... the emitted code should already wrap it... 13:33
fglock, and push @list, \&rule... would just work
fglock ruoso: yes, but Pugs::Grammar::Rule is a bit odd (it's not emitted automatically) 13:34
ruoso fglock, but it should represent the same thing, shouldn't it? 13:35
fglock ruoso: [OT] where does gnome mounts a SMB share? 13:36
ruoso fglock, it doesn't
fglock, that's the great shit of gnome vfs 13:37
fglock, and that's why I pray for hurd every day on my like
s/like/life/
fglock ruoso: it represents the same thing, at high level - put p5 can't have method==object
pmurias ruoso: ever heard of FUSE? 13:38
13:39 elmex joined
ruoso pmurias, yes... Yeat Another Linux Kernel Dirty Hack 13:39
fglock, but... are rule methods accessed any other way than as rule objects? 13:40
fglock ruoso: $grammar->rule() vs. $rule() 13:42
ruoso fglock, ah ok... I got confused again... 13:44
so... push @list, rule should have a different syntax, shouldn't it? 13:46
or one could tie @list to something that makes it work 13:47
fglock ruoso: not sure - I think it should just be emitted in a different way 13:48
13:49 kisu joined
ruoso fglock, tie in the emitted code 13:49
turn "my Rule @list;" into the tie code... 13:50
fglock, what do you think?
ruoso thinking again 13:52
fglock, in "my $rule = rule { ... }"... which value would have $rule? 13:57
fglock ruoso: $rule is a Pugs::Compiler::Rule object 14:02
ruoso fglock, so... doesn't $grammar->rule->() makes sense? 14:03
pmurias, named captures already are written as $<name> 14:06
pmurias, this is one of the problems
fglock ruoso: what if I mix objects and methods in @array? 14:09
ruoso fglock, good question... 14:11
fglock, I added a 'return '' unless defined $n;' in P::E::R::P5::emit_rule 14:16
before the die "unknown node" 14:17
fglock ruoso: but that is an error in the AST - you should emit a warning 14:18
pmurias i'll take a break from the computer now, if someone check why does the make program AST leak into the PCR while compiling Rules.p6 I'll be gratefull
ruoso fglock, hmmm... I noticed it now...
fglock, the rules simply were not there... :)
14:20 b_jonas joined 14:21 Qiang joined
pmurias s/make/main/ 14:22
ruoso fglock, how should literals appear in a rule AST? 14:27
fglock, 'term' => '\\)'
unknown node: $VAR1 = '\\('; 14:29
fglock ruoso: escaped chars are not defined yet in PCR - see the 'XXX' in the grammar 14:30
ruoso fglock, oh... ouch...
fglock, any workaround?
fglock ruoso: I can implement it - one sec 14:31
14:39 chris2 joined
fglock ruoso: done - I'll write some tests now 14:41
svnbot6 r9680 | fglock++ | pX/../PCR - escaped chars (untested)
ruoso constant( '\(' ) 14:42
fglock, shouldn't it be constant('(') ? 14:43
fglock ruoso: testing... 14:45
ruoso: fixed - committing 14:47
ruoso fglock, nice... thanks... 14:48
svnbot6 r9681 | fglock++ | pX/../PCR - fixed escaped chars; tests
r9682 | fglock++ | pX/../PCR - '\n' escaped char 14:55
obra seen nothingmuch? 14:57
15:02 bsb joined
svnbot6 r9683 | fglock++ | pX/../PCR - updated comments, TODO 15:02
ruoso fglock, 'Not a SCALAR reference' at 'sub { ${ $grammar->p6ws( @_ ) } }' 15:06
15:08 b_jonas joined, vel joined, nothingmuch joined
svnbot6 r9684 | ruoso++ | Huge refactoring... importing work from lrep-pcr (pmurias++) to here... going further... It is broken by now... I still didn't understand why... 15:14
ruoso fglock, why does it try to dereference to scalar if it is a code? 15:16
15:17 iblechbot joined
svnbot6 r9685 | ruoso++ | updating TODO 15:20
ruoso fglock, lrep-compiler has the most up-to-date in svn... there is this 'not a scalar reference' problem... please take a look if you have some time
pmurias, I took the work you were doing in lrep-pcr back to lrep-compiler... there is this problem I explained to fglock... but it's almost there... 15:21
ruoso have to go for lunch... 15:25
15:29 justatheory joined 15:31 particle_ left 15:56 nothingmuch joined 16:01 frobnitz joined 16:02 FurnaceBoy joined 16:19 b_jonas joined 16:21 kisu joined 16:29 stennie joined 16:41 Ara4n joined
Ara4n audreyt: ping? 16:41
16:43 KingDiamond joined 16:46 b_jonas joined 17:06 b_jonas joined 17:10 ruoso joined 17:12 willie0220 joined
svnbot6 r9686 | fglock++ | Pugs::Grammar::Base update 17:14
17:16 DesreveR joined 17:17 gilby joined
ruoso fglock, ? 17:19
fglock ruoso: hi
ruoso fglock, what does ``sub { ${ $grammar->p6ws( @_ ) } }'' means? 17:20
17:20 willie0220 left
ruoso fglock, it generated this code... and it causes error... 17:20
fglock p6ws returns a match object - $$match returns the data structure 17:21
ruoso fglock, hmmm...
fglock, it says 'Not a SCALAR reference'
17:21 SamB joined, nothingmuch joined
fglock ruoso: don't reuse the p6ws method in the rule grammar - it was generated by the 'broken' PCR/lrep 17:22
did you compile p6ws yourself?
ruoso fglock, no
fglock, I still need to recompile the lrep grammar 17:23
fglock, if p6ws shouldn't be used, what should be?
fglock, or should I define a new p6ws method?
fglock ruoso: we'll need to write a grammar compiler, in order to fix PCR::Rule 17:24
ruoso: yes, defining the method yourself will be fine
ruoso fglock, lrep is a grammar compiler...
fglock, ok
fglock ruoso: but it doesn't use PCR, so PCR thinks it's broken 17:25
ruoso have a meeting now
17:30 gilby joined 17:44 justatheory joined 17:49 mj41_ joined 18:19 GabrielVieira joined
GabrielVieira ho there 18:19
*hi
18:24 nothingmuch joined 18:26 amnesiac joined 18:28 bernhard joined 18:44 stevan joined 18:45 GnuVince joined 18:47 GnuVince left 19:11 KingDiamond joined, justatheory joined 19:14 KingDiamond joined
fglock ugh - "Unknown error / Compilation failed in require. / BEGIN failed--compilation aborted." 19:15
19:17 GeJ joined 19:40 DesreveR is now known as r0nny 19:53 larsen joined 20:03 chris2 joined, Limbic_Region joined
ruoso fglock, now, after fixing p6ws (at least I think I fixed it), it just doesn't match anything... 20:18
fglock ruoso: I have compiled a grammar with lrep+PCR - now I'm trying to integrate the compiled grammar back into PCR 20:20
ruoso: I'll paste the p6ws I've got here 20:21
ruoso ok
pasteling "fglock" at 200.17.89.80 pasted "p6ws (p5)" (12 lines, 341B) at sial.org/pbot/16448
fglock this was compiled with my current PCR/lrep 20:22
(which doesn't work)
20:25 m joined 20:29 chris2_ joined 20:31 chris2_ is now known as chris2
ruoso fglock, still doesn't work... 20:32
ruoso have to work now...
:(
it really does not match anything 20:44
20:44 pjcj joined 20:47 hexmode joined
fglock ruoso: my version is passing some internal tests already, but it is still too broken for committing 20:48
ruoso fglock, ok... I'm a little bit busy now... 20:49
fglock, but it seems it's all PCR fault now :) 20:50
fglock ruoso: can you paste your p6ws? 20:51
ruoso fglock, please leave a BUGS file with some help if I come back and you're not here...
fglock, the same as yours
fglock, it was like that already
fglock, but I have to work now... I'll be back later... and I'll probably work on it... 20:52
fglock, if you like, I can help you in PCR when I come back 20:53
fglock ruoso: sure
ruoso fglock, just leave some pointers somewhere...
so I can know what to do... 20:54
fglock ruoso: I'll try to make a PCR-dev dir
ruoso ok
fglock ruoso: I spent a few hour to find out what 'Unknown error' was about :( 20:55
hours 20:56
ruoso fglock, :) that's the fun of debugging .... heh
fglock, when you hit your head on the table
fglock, hmmm... looking better... I think it still can be my fault... 20:57
:)
fglock ruoso: does it pass all tests?
ruoso fglock, PCR? yes 20:58
lrep I can't even compile...
pmurias C 21:00
C 21:01
ruoso fglock, hmmm... I can't find where I'm wrong 21:08
fglock ruoso: write a test file and run it with PCR alone 21:09
ruoso hmmm... I think <rule>* is matching nothing and just returning 21:10
ruoso have to work.... really... :) 21:15
Juerd debian-- # your netinst images SUCK
Busybox is NOT ENOUGH. 21:16
And debian-installer's partitioning/raid/lvm thing is way too tedious.
21:16 mj41__ joined
svnbot6 r9687 | ruoso++ | trying to figure out whats wrong... 21:17
wolverian submit bugs?
ruoso fglock, if I change * to + the match returns undef... 21:18
Juerd wolverian: Was that meant for me? 21:19
wolverian yes.
Juerd wolverian: Won't help. If they agreed, they wouldn't have made these sucky cd's. 21:20
Juerd goes to find out how to debootstrap a different arch from the running arch
wolverian Juerd, someone else might read the bug report and get ideas. who knows.
Juerd I don't believe in that.
21:21 FurnaceBoy_ joined
ruoso Juerd, debootstrap already does it... 21:21
Juerd Good. 21:22
Back to manual installations, again.
At least then you get something that:
a. works
b. works in time
c. understands perl
d. can be automated easily
And then I can install it remotely, which means I don't have to listen to the extreme noise this 1U box makes 21:23
fglock ruoso: compiling a language using itself was not supposed to be easy, right? :( 21:24
ruoso: circularity means the bugs can be anywhere 21:25
ruoso: they are actually everywhere
Juerd Oh, and vi 21:26
vim, even
nano sucks
fglock Juerd: I use nano a lot (and vim, gedit, scite) 21:28
21:28 ghenry joined
Juerd fglock: Then you suck :) 21:29
fglock "you are what you eat" 21:31
21:43 m joined
svnbot6 r9688 | fglock++ | pX/.../PCR/PCR-dev.tar.gz - compiles it's own grammar; bugs! - some 21:43
r9688 | fglock++ | matches return undef
21:50 ruz joined
fglock ruoso: now I know what are most of the errors - I'll restart the grammar migration stepwise 21:52
ruoso: I can't replicate the errors you found (p6ws, +/*) 21:53
later & 21:54
21:54 fglock left
svnbot6 r9689 | ruoso++ | this way it simply doesnt work 22:07
22:10 GabrielVieira joined 22:16 justatheory joined 22:21 Limbic_Region joined 22:35 FurnaceBoy_ is now known as FB|afk 22:44 Blues-Man joined
Blues-Man hi 22:46
22:47 Blues-Man left 23:03 siosiosios joined, diotalevi_ joined 23:04 hlen joined 23:10 jisom joined
Ara4n Juerd: you playing with my ghastly xul/flash takahashi hack? 23:15
Ara4n is keeping half an eye on his apache logs
(when his DSL isn't dead, that i)
is) 23:16
Juerd Ara4n: No
Ara4n fairenough 23:18
Ara4n just interested to know if it's gone and segfaulted any more innocent GREs
23:34 rgs joined 23:36 FB|afk is now known as FurnaceBoy 23:46 whiteg joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!