Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: enabled syntax highlighting and fixed small typo error #83

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

chore: enabled syntax highlighting and fixed small typo error #83

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e8bf86f
enabled syntax highlighting
0xflotus Nov 18, 2020
41eeb40
fixed small typo error (#1)
0xflotus Nov 18, 2020
20a975f
enabled syntax highlighting (#2)
0xflotus Nov 18, 2020
8c9a36e
fixed small error (#3)
0xflotus Nov 18, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/CompilerDesign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Problems:
* some optimizations seem to be better suited by a new 'pass' - they don't seem to fit well into the existing model
* some blurring of where python is injected. 'semantic analyzer' actually does some pseudo-codegen operations.
* AST actually has some pseudo-codegen too - FunctionNode() generates a function header
* makes some optimizations more complex - one simple spitfire expression becomes a large chunk of python psuedo-code that is tricky to optimize
* makes some optimizations more complex - one simple spitfire expression becomes a large chunk of python pseudo-code that is tricky to optimize

# 0.7.x #

Expand All @@ -26,4 +26,4 @@ Goals:

Specifics:
* remove pseudo-codegen and replace it with a richer abstract syntax
* use more specific nodes to control code generation
* use more specific nodes to control code generation
4 changes: 2 additions & 2 deletions doc/SpitfireInstallationInstructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Quick Installation Notes #

Copy this code into an file called example.spt:
```
```html
<html>
<head>
<title>Spitfire example</title>
Expand All @@ -23,7 +23,7 @@ Run the compiler on your example file.
spitfire-compiler example.spt
```
This will produce a file called example.py. Now start up your python interpreter and try the following:
```
```python
import example
data = example.example(search_list=[{'name':"Trurl"}]).main()
print data
Expand Down
4 changes: 2 additions & 2 deletions doc/SpitfireSearchResultsExample.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
This is a basic search template that I use a few hundred times a day in my desktop search tool.

```
```html
#from spitfire.runtime.filters import escape_html
#filter escape_html
<html>
Expand Down Expand Up @@ -35,4 +35,4 @@ This is a basic search template that I use a few hundred times a day in my deskt
#end for
</body>
</html>
```
```
4 changes: 2 additions & 2 deletions doc/SpitfireVsCheetah.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ There are a number of directives that have been omitted, at least for the time b
* #assert
* #breakpoint
* #cache
* #compiler-setttings
* #compiler-settings
* #include
* #del
* #echo
Expand Down Expand Up @@ -99,4 +99,4 @@ These are handled a little differently internally to avoid issues like double-es

### Filters are implemented differently. ###

The API is very simple, so it's probably just easiest to look at the code.
The API is very simple, so it's probably just easiest to look at the code.