<please_help>In my symbolic computation framework, I generate a large computation tree that includes multiple bindings at various points in the computation. I currently use symbols to denote variables, but with the dynamic-programming-like approach I have to use due to resource limitations, I need some way to obtain a variable's "reference-list", otherwise I get a <- b <- c; da/db = 0 where I want da/db = 1 (but db/da = 0). <please_help>what's the best way to do that? I think analyzing the tree itself is not tractable. ***karswell` is now known as karswell
***michel_mno_afk is now known as michel_mno
<davexunit>sums up in a couple of pages of text why using appropriate data types avoids many common sources of bugs <davexunit>in the case of the web, XSS vulnerabilities, SQL injection, etc. <taylanub>you would think what's explained on that page is programming 101 :( I did a little bit of MySQL/PHP/JS programming (the standard tools) a few times, and the abuse of strings for data communication is just utterly awful. I remember at least one time it lead to a hard to find bug too. <davexunit>I see it *a lot* in the JS at work that does stuff with jquery. <davexunit>concatenating strings together to form an html snippet and passing it to jquery to render. <davexunit>I'm pushing for things like MithrilJS that provide a nice api to building "virtual DOM" nodes <davexunit>and when rendered all the escaping is handled for you <taylanub>davexunit: have you looked into ClojureScript? I might start working at a Clojure shop soon, possibly with ClojureScript for web dev included, dunno what to expect. <davexunit>I'm honestly not all that interested in compile-to-js languages. <davexunit>I just use regular javascript with its warts. <davexunit>that said, clojurescript is surely an improvement. ***michel_mno is now known as michel_mno_afk
***michel_mno_afk is now known as michel_mno
***michel_mno is now known as michel_mno_afk
<paroneayea>davexunit: totally understand both flying anxiety and the expense of going overseas reluctance, but if you have the opportunity to do it and esp if a Guile track happens, FOSDEM is totally worth it <davexunit>sucks when something gets to the front page but no one comments. <daviid> davexunit: about HN, it's kind of holiday time worldwilde, and the title could be more provocative :) "Don't let evils hide nasties in your html strings, use sxml instead!" <daviid>which is why nobody is getting involved in my opinion <davexunit>maybe paroneayea and I can get a sexp SQL thing going <davexunit>since each database uses its own language, even if things look similar <daviid>why not sql first, then specific module(s) for postgresql, so I could use it with sqlite3 <davexunit>I'm unsure if simple sexps are the best data structure to use <davexunit>so you can more easily create composable procedures. <daviid>davexunit: sql is very well defined, implementation may differ, but not the core of sql itself. you prob wantd to refer to extension(s), but that precisly should handled in modules, imo. chicken does that by the way, 'core sql' and postgresql extension <davexunit>well, for example, mysql and postgresql don't even agree on string literals. <davexunit>so yes, perhaps there can be some generic base interface, but you'd still have to define pretty much everything for each languge. <davexunit>for experimentation, I think focusing on a single database will prove easiest, and then the design can be evaluated and generalized. <daviid> really don't think so. you mean the way to pass the string to the db will vary, sure but in moist cases, not the query itself, at least not for 90 maybe 95% of the cases <davexunit>the syntax of string literals is different, postgresql is single quotes only, for example. <daviid>ssql should not even have connectors imh, 'just' an ssql-sql engine <daviid>no dsependency to any db in particyular <davexunit>anyway, we're arguing about details of an implementation of something that doesn't even exist yet. <daviid>davexunit: iirc, this is an option, pgsql will alsi properly handle double quotes