1. [docs] See the changes for 23Sep2019
- Posted by _tom (admin) Sep 23, 2019
- 1001 views
For 23Sep2019 3 pm these are what the changes to the docs look like:
convert.e
https://docs.google.com/document/d/10s7yCVBoz30IWsa7N4UbwXS61A-qwAxd2MigFpt0-PU/edit?usp=sharing
datetime.e
https://docs.google.com/document/d/1b7-L2nTDzT8IPZn07lyQStRzb3N4bgQpjHCDrn1Tv7M/edit?usp=sharing
using_euphoria.txt
https://docs.google.com/document/d/1RIj74umvmHUIKBQoI2MAYKST7K1QdaEbRw4PLHvBZ8g/edit?usp=sharing
welcome.txt
https://docs.google.com/document/d/1A6pnnAawMa6P4bJ-AWvRntfc4GZ5KtktUQtnqqDzXwc/edit?usp=sharing
_tom
2. Re: [docs] See the changes for 23Sep2019
- Posted by euphoric (admin) Sep 23, 2019
- 1015 views
For 23Sep2019 3 pm these are what the changes to the docs look like:
convert.e
https://docs.google.com/document/d/10s7yCVBoz30IWsa7N4UbwXS61A-qwAxd2MigFpt0-PU/edit?usp=sharing
Thanks, _tom.
I fixed the errant </eucode> in the docs for the float64_to_atom() function example.
Let me know if y'all find any more goofs.
3. Re: [docs] See the changes for 23Sep2019
- Posted by irv Sep 23, 2019
- 982 views
bytes_to_int ignores the fact that include convert.e won't work. It's std/convert.e
The demo doesn't include the include line.
int_to_bits says include convert.e (should be include std/convert.e)
the demo doesn't include the include line. the demo doesn't declare variable s
bits_to_int has the same problems, invalid/missing includes, undeclared variable a
Most of the demos have problems with the headers, as in the example below.
include convert.e -- where is the std/ ? namespace convert public function atom_to_float64(atom a)
4. Re: [docs] See the changes for 23Sep2019
- Posted by euphoric (admin) Sep 23, 2019
- 961 views
bytes_to_int ignores the fact that include convert.e won't work. It's std/convert.e
int_to_bits says include convert.e (should be include std/convert.e)
bits_to_int has the same problems, invalid/missing includes, undeclared variable a
Looks like some of these are duplicates of tickets. You might want to delete any dupes from either side to avoid duplicated and lost effort.
Thank you!
5. Re: [docs] See the changes for 23Sep2019
- Posted by ChrisB (moderator) Sep 24, 2019
- 937 views
Hi
So is it ok to edit these examples so that a copy paste actually produces a working example (where possible)?
Cheers
Chris
6. Re: [docs] See the changes for 23Sep2019
- Posted by _tom (admin) Sep 24, 2019
- 942 views
Hi
So is it ok to edit these examples so that a copy paste actually produces a working example (where possible)?
Cheers
Chris
Please do so.
I strongly believe that all examples must run. The output should be shown. I use --> to show the output on the next line.
For a built-in:
puts(1, "hello") --> hello
For a std/lib:
include std/console.e display( "hello" ) --> hello
If you must provide a code snippet, make it clear it is incomplete:
-- ... atom fn = open( "data.txt" ) ? results -- ...
(Not sure if -- ... is the best visual clue; use something like it.)
_tom