An error while making progman.pdf and a couple of questions
Rayne
or lyx guy, so I'm not sure what's wrong here.
rayne@rayne-desktop:~/slate-language/doc$ make progman.pdf
lyx -e pdf progman.lyx progman.pdf
unusual contents found: [char " mathalpha][char g mathalpha][char o
mathalpha][char l mathalpha][char d mathalpha][char " mathalpha][char
+ mathalpha][char " mathalpha][char f mathalpha][char i mathalpha]
[char s mathalpha][char h mathalpha][char " mathalpha][char =
mathalpha][char " mathalpha][char g mathalpha][char o mathalpha][char
l mathalpha][char d mathalpha][char f mathalpha][char i mathalpha]
[char s mathalpha][char h mathalpha][char " mathalpha]
unusual contents found: [char " mathalpha][char f mathalpha][char i
mathalpha][char s mathalpha][char h mathalpha][char " mathalpha][char
+ mathalpha][char " mathalpha][char g mathalpha][char o mathalpha]
[char l mathalpha][char d mathalpha][char " mathalpha][char =
mathalpha][char " mathalpha][char f mathalpha][char i mathalpha][char
s mathalpha][char h mathalpha][char g mathalpha][char o mathalpha]
[char l mathalpha][char d mathalpha][char " mathalpha]
Warning: Index sorting failed
----------------------------------------
LyX's automatic index sorting algorithm faced
problems with the entry '˜== (message)'.
Please specify the sorting of this entry manually, as
explained in the User Guide.
make: *** [progman.pdf] Error 1
Also, this link: http://www.slatelanguage.org/doc/progman.pdf is dead.
I've never used a language like Slate before, so I'm not used to the
whole 'image'-based programming scheme. I'm not sure how I should go
about writing my code. Is the entire application supposed to be made
up of evaluated expressions in the REPL? What should be put in files,
if anything at all? The tutorial is quite brief, and the
GettingStarted tutorial is quite complicated, so I'm a little
confused. :p
Finally, how would one write a command-line script or something of
that sort?
Timmy Douglas
On Mar 12, 11:26 pm, Rayne <disciplera...@gmail.com> wrote:
> I git pulled this straight from the github repo, and I'm not a Latex
> or lyx guy, so I'm not sure what's wrong here.
> [snip]
> Also, this link:http://www.slatelanguage.org/doc/progman.pdfis dead.
well progman is probably out of date anyways, you might want to try
rosettacode for a more gentle introduction.
http://rosettacode.org/wiki/Category:Slate
> I've never used a language like Slate before, so I'm not used to the
> whole 'image'-based programming scheme. I'm not sure how I should go
> about writing my code. Is the entire application supposed to be made
> up of evaluated expressions in the REPL? What should be put in files,
> if anything at all? The tutorial is quite brief, and the
> GettingStarted tutorial is quite complicated, so I'm a little
> confused. :p
The slate vm runs the image similar to how the OS runs the vm (or any
executable).
The slate image contains all slate code and objects. Put your code
into files as
you would with any language and load it into the slate image to test.
> Finally, how would one write a command-line script or something of
> that sort?
like a bash script except with #!/path/to/slate
at the top.
Rayne Simpson
a Slate application, presumably on Linux?
Timmy Douglas
On Mar 13, 10:46 am, Rayne Simpson <disciplera...@gmail.com> wrote:
> Alright, thanks. One more thing: what is the preferred way to distribute
> a Slate application, presumably on Linux?
You could give them your image, a VM, and any necessary DLLs.
Rayne Simpson
API documentation for Slate? If progman is outdated, what should one use
to find what they're looking for?
Timmy Douglas
if you want to get a list of methods using a particular object, for
example, a string, you could do this:
'hi' methodsUsingMe.
If you want to see something defined on just "String traits" you could
do:
String traits roles collect: #selector `er.
and then:
slate[52]> (#escaped findOn: {''}) method definitionLocation.
'src/core/string.slate:322'
slate[53]> (#escaped findOn: {''}) method sourceTree.
s@(String traits) escaped
[
"(snipped)"
].
you could also browse the src/lib and src/core directories for basic
stuff.