01:31 -!- Prax01D(n=Prax01D@149.99.96.13) has joined #maxima 01:47 -!- istefano(n=istefano@65.39.87.25) has joined #maxima 03:43 -!- trebor_h_(n=trebor@dslb-084-058-223-138.pools.arcor-ip.net) has joined #maxima 05:22 -!- lisppaste4(n=lisppast@common-lisp.net) has joined #maxima 06:06 -!- emma(n=emma@user-12lcol5.cable.mindspring.com) has joined #maxima 06:37 -!- stw__(n=stw@e176169078.adsl.alicedsl.de) has joined #maxima 07:35 -!- Prax01D(n=Prax01D@tor58-4-74-168.dynamic.rogerstelecom.net) has joined #maxima 09:18 -!- szymon(n=szymon@bzm16.neoplus.adsl.tpnet.pl) has joined #maxima 10:28 -!- ASau(n=user@79.111.10.47) has joined #maxima 12:41 -!- grandrew(n=grandrew@91.78.33.75) has joined #maxima 12:42 hi all! how can i make maxima not pretty-print output - i mean, return x^2 and a/b instead of 'like paper-written'? So I could copy-paste it into real program? 12:47 -!- cunzhang(n=chatzill@218.7.43.195) has joined #maxima 12:48 grandrew: "display2d : false;" 12:49 grandrew: or "tex(a/b);" for TeX output you can include in your LaTeX document 13:03 thanks! 13:08 -!- ASau(n=user@79.111.18.27) has joined #maxima 13:08 and why does maxima change y1 to Y1 in results output while x1 remains unchanged? 13:12 grandrew: interesting, how can i reproduce that? 13:14 solve([y2s = m*x2s + b, l^2=(x2s-x1)^2 + (y2s-y1)^2], [x2s, y2s]); 13:14 makes my y1 change case to Y1: 13:14 (%o25) [[x2s = -(SQRT(-Y1^2+(2*m*x1+2*b)*Y1-m^2*x1^2... 13:15 maybe that's because i'm using some extremely old maxima version 13:15 grandrew: doesn't happen here: http://rafb.net/p/l7fNva39.html 13:17 okay. I'll assume it's my old maxima bug. I was just wondering if it indicates any computation errors 13:17 5.14.0 doesn't too 13:17 5.10.0 here 13:18 grandrew: my guess is that you have defined some of those variables to be Y1 13:18 5.9.1 :-) 13:18 grandrew: i can reproduce that 13:18 just tested with 5.9.1 and I see "Y1". 13:19 hm okay. hope this just doesn't affect results if i take them case-insensitive 13:20 lindi-, you're having all maxima versions installed? are you maxima guru? :-) 13:21 grandrew: no i just have debian oldstable, stable and unstable in chroots 13:22 hah cool 13:27 so i can just say "sid maxima" to run the unstable version (where sid is wrapper for schroot -c sid -p -q -- "$@") 13:38 -!- Prax01D10D(n=Prax01D@tor58-7-82-184.dynamic.rogerstelecom.net) has joined #maxima 14:33 I have seen projects/channels on Freenode some times offer their members/users a cloak that they can use on Freenode. Like for example: Tooby-Wan (n=ToO@wikinews/Tooby) is a cloak someone has from the wikimedia people. I am a user of Maxima and a hopeful future contributor, so could Maxima have a cloak and could I get one? 14:37 emma: i am not sure if any maxima developers visit this channel at all 14:37 Harald G does. 14:42 good to know 15:19 -!- szymon(n=szymon@bzv33.neoplus.adsl.tpnet.pl) has joined #maxima 17:17 -!- Sharpie(n=sharpie@bzq-79-182-159-172.red.bezeqint.net) has joined #maxima 17:18 how can i get a numerical result? (like, the full number instead of 1.354619*10^-8) 17:19 Sharpie: "1/2,numer;" 17:21 nope, still gives me 1.3546190035842542*10^-8 17:21 Sharpie: what is the input? 17:21 i want a number (like,0.000000001) 17:21 let's say the input is 1.3546190035842542*10^-8 17:24 (%i16) printf(false, "~f", 1.3546190035842542*10^-8); 17:24 (%o16) 0.000000013546190035842542 17:28 hm, i'm using wxmaxima, do you know how to do that here? 17:28 Sharpie: you can just type 'printf(false, "~f", 1.3546190035842542*10^-8);' there surely? 17:29 brings up an error 17:29 Sharpie: what error? 17:29 Could not find `stringproc' using paths in file_search_maxima. 17:30 interesting 17:30 i think you need newer maxima 17:30 5.13.0 works, 5.10.0 doesn't seem to 17:32 i have 5.12.0 17:35 Sharpie: What is the point of using obsolete release? 17:35 that's the version in the repo =[ 17:35 debian stable has 5.10.0 17:35 ubuntu has 5.12 17:35 Use other package managers then. 17:35 Which don't lag behind progress that much. 17:36 Or nag your distributors. 17:36 Sharpie: just setup chroot for debian unstable for example 17:36 Sharpie: http://iki.fi/lindi/schroot.txt has examples 17:41 i'll just compile maxima from source then 17:41 Sharpie: that's not so good, you can't report bugs to distributions then :) 17:41 Sharpie: install pkgsrc (pkgsrc.org) and get in touch with progress. 17:42 We do most of things for you. 17:43 lindi-: you can. 17:43 First bug is "* distributes long time obsolete Maxima, please fix it." 17:44 ASau: i meant that if you download maxima manually and build it yourself then you can't really report a bug against the package which you did not use at all 17:44 lindi-: you can. 17:44 Bug report formula is: 17:45 " distributes long time obsolete Maxima." 17:45 ASau: i want it to distribute 5.10.0 17:45 This is a bug. 17:45 i consider it a feature :) 17:45 That means that your distribution is obsolete as well. 17:46 bits don't get old :) 17:46 ASau what are you using? 17:46 There're a number of bugs fixed since 5.10. 17:46 Sharpie: I use NetBSD. 17:46 hardcore. 17:46 ASau: yep, and that's why i use 5.13.0 too 17:47 5.14 is compiling as we speak =o 17:47 I use 5.14.0, which is the current official package. 17:47 there all done 17:47 now i'll compile the new wxmaxima =o 17:48 the whole process will probably take less time than removing ubuntu and installing BSD 17:48 You can use pkgsrc on Ubuntu. 17:48 would rather not to. 17:48 It's Debian inside, IIRC, and someone run pkgsrc bulk builds for Debian. 17:49 Sharpie: I prefer pkgsrc to gnu/linux package management. 17:49 wow, wxmaima is taking more time to compile than maxima 17:49 It is more modern and average time to fix bug is around 10 days. 17:49 and it's about 1/20 its size 17:50 there, now i have wxmaxima 0.7.4 and maxima 5.14 17:51 now how can i simplify 1.3546190035842542*10^-8? :/ 17:51 I've got fed up with various linux-based distributions in past. 17:51 we can see that :) 17:51 If you want to get the "0.000000013546190035842542" result, 17:51 use what was proposed above. 17:51 i kinda lost it 17:52 printf(false, "~f", 1.3546190035842542*10^-8); 17:52 and it's kinda harder to find things in irssi 17:52 thx. 17:52 < lindi-> (%i16) printf(false, "~f", 1.3546190035842542*10^-8); 17:52 -!- sharpie_(n=sharpie@bzq-79-182-159-172.red.bezeqint.net) has joined #maxima 17:52 accidently pressed ctrl-z 17:52 anyway, it prints um 17:53 1.3546190035842542e-8 17:53 Sharpie: which lisp interpreter? 17:53 lindi um 17:53 not sure rly 17:54 just whatever was in the repo 17:54 It prints in the startup banned. 17:54 Sharpie: you didn't use the same packaging scripts that debian unstable uses? 17:54 ...banner. 17:54 Using Lisp CMU Common Lisp CVS release-19a 19a-release-20040728 + minimal debian patches 17:55 Sharpie: debian unstable uses GCL 17:55 too bad i don't have it :/ 17:55 Sharpie: apt-get build-dep maxima? 17:55 Sharpie: it'd be a lot easier to just use debian unstable chroot 17:55 but i already installed and compiled maxima 17:56 Sharpie: but with the wrong lisp interpreter maybe? ;) 17:56 there's only 1 in the repo 17:56 Well, CMUCL is among the fastests. 17:56 (when this technical discussion winds down, I would like to ask some philosophical questions about Maxima, just give me a signal for when that would not be rude :) ) 17:56 emma: heh 17:56 emma: just ask. 17:57 well, nobody knows how to simplify it then? 17:57 other than the printf command? 17:57 We can answer it later. 17:57 No no i don't want to interrupt an important conversation. 17:57 Sharpie: what is simpler than the number?? 17:57 well, i want the full number 17:57 instead of 1.3546190035842542e-8 17:57 What does "full number" mean?? 17:58 0.000000047831947289whatever 17:58 with leading zeroes 17:58 Okay then: I was wondering what is the advantage of Maxima being written in Lisp? Could Maxima be written in Scheme? And could Maxima ever be re-written in another language? What would be some advantages of re-writing it in another language? 17:58 Sharpie: That's just another denotation, the number is the same. 17:58 ASau: i'm well aware of that, nevertheless i need the full number 17:59 emma: the advantage is the existense of Maxima. 17:59 emma: i haven't yet managed to debug maxima under slime, i don't know the code base well 17:59 emma: Scheme didn't exist, when MACSYMA started. 17:59 Please don't let these little questions out of curiosity interrupt the serious technical discussion. :) 18:00 BTW, lindi-, is there a way to trace backend lisp evaluation? 18:00 I'm trying to find it in the documentation for a month! 18:01 (I don't have much time to spend on it.) 18:01 ASau: i have only tried to debug using slime 18:02 I know Scheme did not exist back then. But Scheme exists now. Could Maxima be written in Scheme? 18:02 Could Maxima be re-written in Java or Python (just two pick two at random)? 18:02 emma: no point in doing that. 18:02 lindi-: well, any pointer? 18:02 lindi-: any success? 18:03 Might there be a benefit in the sense that the intersection of people who are very competent in math and competent in coding is already small, but even smaller when you add the third circle to the venn diagram of being very competent in Lisp? 18:03 -!- szymon(n=szymon@cam203.neoplus.adsl.tpnet.pl) has joined #maxima 18:03 ASau: http://iki.fi/lindi/clisp/README is about my "how to get debugging symbols" experiments 18:03 This is not a statement, since I surely do not know, but if Maxima were re-written in Python might there be lots more developers working on it? 18:03 ASau: and http://iki.fi/lindi/maxima-debug.txt 18:03 ASau: it seems that somehow the core that is dumped to disk just does not have the debugging information 18:04 emma: well, if i could debug it with slime it'd be easy for me to contribute 18:04 emma: no point in rewriting it in Python, Lisp is better. 18:05 i'm sure some developers must be using slime to debug it 18:05 can't find anything in the documentation either =\ 18:08 Sharpie: if you want comparison of Lisp implementations, 18:08 here's a sketch: 18:08 ASau: ...talking about my exponential problem 18:08 there exist 4 major opensource players: 18:09 ASau: i don't care about lisp 18:09 CLISP, GCL, CMUCL, SBCL. 18:09 SBCL is the best, GCL is the worst. 18:09 ASau: stop 18:09 CLISP is the most portable. 18:09 1.3546190035842542e-8 18:09 make this a number. 18:09 It is a number already. 18:10 make this a number without exponents 18:10 and GCL does not call itself "open source" :) 18:10 (couldn't resist) 18:10 GCL is opensource, but it is the worst opensource Lisp. 18:11 I didn't look at ABCL, but I don't think it deserves comparison. 18:11 For my needs I want native implementation. 18:11 Java isn't portable enough. 18:12 Sharpie: what is wrong with printf? 18:12 it doesn't work 18:12 I see, that it does. 18:13 not over here 18:13 Right over here. 18:13 it is probably passed to the lisp interpreter 18:13 Sharpie: So, you should explain exactly, what you want. 18:13 i think he wants zeroes 18:13 ??? 18:13 and no "e" 18:13 indeed. 18:13 Is Maxima written in the kind of Lisp that most people who know Lisp are comfortable with? 18:14 emma: right. 18:14 emma: common lisp is pretty standard yes 18:14 i want 1000 instead of 1*10^3 18:14 Why can't lindi- work out the Lisp when he seems to know Lisp? 18:14 Is there any way that Maxima could be re-written in Scheme? 18:14 or in this case, 0.something instead of 1.3546190035842542e-8 18:14 emma: since i can't figure out the build system to include debugging symbols 18:14 emma: the problem isn't in Lisp here. 18:15 emma: rewriting in other language requires far more understanding of both languages. 18:15 emma: it requires more man power and more effort as well. 18:16 ASau: if you ever figure out how to debug maxima using slime please let me know :) 18:16 lindi-: alright. 18:16 ASau - it would sure be a huge undertaking, but maybe if it had a pay off it could be worth it. 18:16 emma: it doesn't worth it. 18:17 1. Lisp is better than Python. 18:17 I was just thinking, imagine Maxima written in a language that was a little less byzantine to most people, then there would be more people who could help? 18:17 Lisp is easier to use than Python. 18:17 emma: lisp is not so difficult to learn really 18:17 emma: the tools could just be nicer 18:18 Python has major problems with difference between data and language. 18:18 None of what I'm saying is said from any experience or knowledge, I hope I don't come across that way. 18:18 It does matter for CAS. 18:19 I will tell you all (and this Harald G bot) a little secret. Until about 5 months ago, I didn't know anything about any of these things. But then I switched to Linux, stumbled into IRC, learned about Maxima, thought Maxima was the most wonderful thing ever (a gift to humanity), learned that Maxima is written in Lisp, and now I am trying to learn my first programming language :) 18:20 maxima is definitely not perfect :) 18:20 It will be eventually. 18:20 isn't lisp a bit obsolete? 18:20 I went to learn Lisp but they recommended I start learning Scheme because there are good educational resources. 18:21 emma: if you learn scheme it's not difficult to learn (common) lisp after that 18:21 So as my first programming language I'm trying to teach myself Scheme. That's why I wondered if Maxima could be re-written in Scheme :) 18:21 why not learn any of the mainstream languages? (c/c++/python/java) 18:21 Sharpie: Lisp isn't. 18:21 and emma, it would take years of experience to be able to rewrite maxima 18:21 Sharpie: Python is. 18:21 Sharpie - Read the sequence of events that led to me learning a programming language in the first place. 18:21 emma: gnucash is written in C and scheme, in case you want something practical to study :) 18:22 Why would I learn a programming language that Maxima is not written in? 18:22 lol 18:22 yup, i love the bible 18:22 emma: to learn :) 18:22 I'm not joking. 18:22 why would i wear clothes people there didn't 18:22 :) 18:22 emma: scheme is so much more compact 18:22 emma: you better start with it 18:22 and actually, i like comic books 18:22 why would i not be 2D 18:22 I did start with Scheme I feel like it's a Lisp so it's not wasted time. 18:23 Hopefully when I know Scheme it won't be so hard to learn CL so I can understand Maxima. 18:23 you can't become an experienced programmer overnight 18:23 But I have some ideas for how I would like to help Maxima in the meantime until I know Lisp. 18:23 actually you know what, it's a great idea 18:24 i'll go learn C and rewrite linux 18:24 rewrite it in what? ;) 18:24 I am not aiming to re-write anything. I think you might be mistaking me. :) 18:24 I wondered about the possibility of all of YOU re-writing it into something easier to learn for me :) 18:25 But if that's not helpful over all then, I'll just learn Lisp eventually. It will probably take a while though. 18:26 emma: no such possibility. 18:26 well actually that's a great idea 18:26 emma: think about rewriting UNIX in BASIC. 18:26 it's really hard for me to build my own motherboard 18:26 maybe i'll call ASUS and ask them to make their motherboards out of lego? 18:28 Oh come on guys I was being a little bit light hearted. The question about the feasibility and possible upsides of re-writing Maxima in a more widely known language were sincere, but not just for me. :) 18:29 Since even SAGE refers to Maxima, there's no indication of use of converting to anything else. 18:30 moreover, it's extremely complicated, rewriting a project that's been under construction for over 20 years isn't such a simple thing to do 18:30 The only advantage I can imagine is that if it were written in a more widely used language there would probably be a lot more people putting energy into it. Because Maxima is one of the coolest things ever. 18:30 hmm, just looked at pkgsrc. it seems to requre proprietary sun jvm for compiling eclipse although it has been possible to compile it with gcj for a few years and now we also have icedtea 18:31 emma: Lisp _is_ widely used. 18:31 emma: you might as well call rich stallman and ask him to rewrite gnu/linux in C# 18:31 My guess is that Lisp is a barrier of entry for a lot of people who would be enthusiastic Maxima developers? 18:31 not lisp itself, it's the tools 18:32 lindi-: I don't use java myself, but I'll tell others. 18:32 emma: there're pretty many things to do without Lisp knowledge. 18:32 emma: and Lisp is way easier than Python. 18:32 haha 18:33 I have an idea for something that I am going to try to do independently to help the Maxima project. 18:33 donate money 18:33 ASau, dont you think do really? :-P 18:33 grandrew: I do think that way. 18:33 Who should I send money too? Harald? 18:34 I used Python, I used some old Lisp, I used Common Lisp. 18:34 I used Scheme too. 18:34 Lisp is the only language that I can write programs in but can not understand some of the programs written by pro's 18:35 that's why I fear Lisp 18:35 i have just very basic lisp knowledge, i wish the tools were bit easier to use 18:35 grandrew: same with C and Python. 18:35 ASau, you've got the reverse-polish mind :-P 18:36 python at least seems to be constantly changing which is bit worrying 18:36 Forth is the language I love. :p 18:36 i program with notepad 18:36 and let monkeys execute w/e i write 18:37 ACTION executes whatever you write 18:37 the truth is, Python is much much much easier to program with, but is just completely unsuitable for the tasks maxima solves 18:38 and speaking of the tools, i really like the ocaml debugger where you can go backwards in time 18:39 haha the fourth link at google for 'ocaml' is http://www.podval.org/~sds/ocaml-sucks.html lol 18:40 grandrew: yeah, and that page refers to CMUCL. 18:40 Is there seriously a place to make donations to the Maxima project? 18:40 Who oversees this project? Is there a project manager? 18:41 Would you like to know how I hope to help the Maxima project in the mean time while I have no coding skills? 18:43 you can find almost everything you need at http://sourceforge.net/projects/maxima 18:47 grandrew: Python is a step back to good old FORTRAN days, 18:47 grandrew: I have visual space for more than 100 columns, 18:48 but have to use only first dozens of them just because 18:48 "indentation matters" and you can't write several elementary 18:48 operations in a line. 18:49 ASau, Python is a step forward to a more complete, formal and understandable language 18:49 In any other respects, it doesn't differ from any interpreted language. 18:50 We have formal languages since Algol days. 18:50 and you can separate operatord by; in python. Once I thought 'indentation mattaers' is a bad joke but now i understand the importance of forcing everyone use the single formal writing technique - even in text formatting 18:50 Except PERL and others of that kind. 18:52 This technique leads to breaking lines, containing the 18:52 single conceptual operation, into several ones identically indented. 18:52 ALGOL is not coparable to python in the terms of symbols per action as many other languages 18:52 That's clearly bad, as shown in so-called "Forth horizontal style". 18:53 OTOH, Python isn't comparable to anything of APL family, so what? 18:53 ASau, again, use: python -c "a=1;print(a)" 18:53 APL is formal too. 18:53 grandrew: that's alright, I took the hint. 18:54 Yet the problem remains. 18:54 This indentation-oriented style leads to breaking 18:54 conceptual operations into elementary dust. 18:54 that is not a problem its a feature. You'll understand why if you start coding python great apps 18:56 E.g. "t=a; a=b; b=t" is required to be broken into separate lines, 18:56 and be mixed into the rest. 18:56 grandrew: I used that in Forth, and have understood, that's bad. 18:56 ASau, and speaking of Lisp vs. python the latter is at almost 10x faster in execution. arguable-and-depends though but is true for general coding 18:57 I never noticed speed advantage. 18:57 Forth != Python. I tried forth too and know it is bad not because of indentation 18:58 Probably, SBCL and LispWorks are good in optimization. 18:59 I used Forth, Lisp, C, Python, and see, that Python indentation rules are bad. 18:59 Like any other indentation rules. 18:59 In any language since FORTRAN. 19:00 the only truth I know for Lisp is that I wrote algebraic differentiation, taylor series and some other stuff for my Palm m500 mini-lisp - all took about 800 LOC AFAIR. recetly found the same for python in 10000 LOC. that's true 19:01 Lisp is far better for algebra and AI - what it was designed for 19:02 I don't know what Python is good for, except trivial stuff, like web services. 19:04 haha web services is trivial but important ;-) so are Inkscape and Scipy 19:05 I didn't look at Lisp web frameworks, yet they exist. 19:05 And I did XML processing in Lisp. 19:06 As for numeric stuff, I prefer FORTRAN. 19:06 you can not use Lisp for those due to performance degrade. You COULD use lisp if it showed another 10x in development time decrease but it does not 19:07 I never have seen performance degrade in Python to Lisp switch. 19:07 Performance increased rather well for me. 19:09 the reason I write almost everything in python now is that it is really faster in terms of development time. Faster than everything now available to build anything 'trivial' - a times faster 19:10 Another PERL. 19:10 yep, another 5x perl 19:11 That's why you argue in favour of strict indentation rules, 19:11 it doesn't matter if code readable or not while it is properly indented. 19:12 indentation rules _increase_ readability. Or you can argue that? 19:12 Yes. 19:13 impossible. 19:13 They don't, unless you don't have beautifier. 19:14 Large part of GNU code is unreadable, though properly indented. 19:15 GNU code is C 19:15 So? 19:16 I've seen Python code as well (had to modify it). 19:19 if you code python, you unserstand that indentation rules, no need for { } begin/end - work together and lead to more understandable code. I dunno what code did you meet with that you could hardly understand 19:20 I didn't say, that I hardly understand it, but it was easier to understand, 19:20 btw, if anybody needed the "{} -> indentation" preprocessor for python - it would have been written already. Nobody needs it 19:20 if it was properly formatted, not just formally. 19:21 properly formatted or code properly designed? 19:21 Properly formatted. 19:21 Cf. literate works. 19:21 They are formatted properly, with indentation of logical parts. 19:22 Not just formal ones. 19:23 hm 19:23 Do you think, that's because they're written so, that reader couldn't understand them? 19:24 human languages suck :-P 19:25 English maybe. 19:25 I'm not sure for it. 19:25 oh great! 19:26 Other languages may rock. 19:26 :p 19:27 ok. lets assume Russian rocks and finish the discussion :-p 19:27 Yeah. 19:28 ;) 19:32 -!- Prax01D(n=Prax01D@tor58-5-76-181.dynamic.rogerstelecom.net) has joined #maxima 20:32 -!- grandrew(n=grandrew@ppp91-76-27-75.pppoe.mtu-net.ru) has joined #maxima 20:56 -!- szymon(n=szymon@bzm109.neoplus.adsl.tpnet.pl) has joined #maxima