A development journal on HSQL
This week focused on finishing up documentation, a little bit of cleanup and one final task of implementation that would be helpful. DISTINCT The SELECT DISTINCT clause currently uses a DEDUP(x,ALL), which is notoriously slow for large tasks. Instead an alternative clause was suggested TABLE(x,{<cols>},<cols>,MERGE); //eg. for a t1 table with c1 and c2 TABLE(t1,{t1},c1,c2,MERGE); …
Continue reading “Week 12: Dedup & Documentation (& Examples)”
This week, was adding some more Machine Learning Methods, and a final Presentation for the work I’ve done through this period! Adding More Machine Learning Support A set of other A set of other training methods were also added. GLM was decided to be split into some of its more commonly used components. This expands …
Continue reading “Week 11: Machine Learning Methods and Final Presentation”
This week’s focus was more on getting train and predict working, the last two remaining statements. There were also some minor bugfixes. Declarations Declarations are used on the .dhsql files that we’ve worked on in the past. They’re a really nice candidate for adding in a way for bundles to indicate their train methods. However …
This week has been a big week – extending SELECT to load up datasets from logical files, modules, functions, and running from a CLI was worked on. There’s a lot to uncover! Select from dataset As layouts have now been introduced, one handy way of using select can be added in – loading up a …
This week was focused on creating EXPORT/SHARED to work, and to add over importing from current directory and Layouts. Exports Exports are a very useful feature in any language. The main idea here is to export some data and layouts, that can be reused in another module. Taking a piece from ECL, we can define …
This week’s work was on getting the WRITE statement to work, and extending a DISTRIBUTE extension to SELECT. The rest, was getting some bugfixes and reading. Write The OUTPUT statement in HSQL is intended to be a way to output values to a workunit. In ECL however, OUTPUT can be used to write to a …
This week’s plans were to essentially work on and implement the PLOT statement, and then to see how to update the TextMate Grammar and add in the new syntax. Plots Continuing from last week, we have auto-imports and an AST for Plots. With some little code generation, we can have a functioning PLOT statement. Here’s …
This week’s plan is to work on imports, as a step leading to the implementation of the PLOT statement. The idea is to be able to locate ECL imports, and hint to the compiler what is contained in an ECL file. DHSQL An idea inspired by the relationship between javascript and TypeScript, the idea is …
This week’s work is planned exclusively around getting select to work; its a huge part of the language. The decision, was to use FUNCTIONS, to emulate a SELECT. Why? Because functions in ECL have their own scoping, and local variables declared there, will be usable outside the scope of the function. However, a function cannot …
I started work on the extension first. Needing some changes, I needed two primary features: Syntax checking, and compiling to ECL as a primary featureset. So, I decided to go in order. For syntax checking, the basic process is: The language client keeps sending info about the text documents on the IDE, to the language …
Continue reading “Week 3: Extension, scopes, and planning Select”