1. I do not find in the documentation 4.XX describe GET
- Posted by useful Mar 19, 2014
- 1474 views
http://www.rapideuphoria.com/lib_e_g.htm#get I do not find in the documentation 4.XX describe GET. And also don't understand the logic even with 3.XX(2.XX) proof PRINT(http://www.rapideuphoria.com/lib_p_r.htm#print http://openeuphoria.org/docs/std_io.html#_1571_print) in the number of built-in functions and lack GET among those.
2. Re: I do not find in the documentation 4.XX describe GET
- Posted by useful Mar 19, 2014
- 1417 views
I was looking bad :) http://openeuphoria.org/docs/std_get.html#_2311_inputroutines
But the second part of the question is not about equality and GET and PRINT still interested
3. Re: I do not find in the documentation 4.XX describe GET
- Posted by mattlewis (admin) Mar 19, 2014
- 1405 views
But the second part of the question is not about equality and GET and PRINT still interested
Could you try rephrasing your question, please? I'm not sure what you're asking about. Also, note that the docs on rapideuphoria.com are for 3.1, not 4.0. Click the "manual" tab at the top of this page to get the 4.0 manual.
Matt
4. Re: I do not find in the documentation 4.XX describe GET
- Posted by useful Mar 19, 2014
- 1390 views
The documentation I understood this and have the second message. The second question was not logical from my point of view, the situation in which "print" is included in the built-in functions and "get" is described in "get.e"
I expect that to get historically was written later and no became one of the built-in and is not fair
p.s. In my services I accept the sequence {..., ...} and answer them {..., ...}(as others do it with json or xml). and this is the problem of those who seek to understand the format of standard format strings.
5. Re: I do not find in the documentation 4.XX describe GET
- Posted by _tom (admin) Mar 19, 2014
- 1389 views
The second question was not logical from my point of view, the situation in which "print" is included in the built-in functions and "get" is described in "get.e"
I expect that to get historically was written later and no became one of the built-in and is not fair
It is a "design choice" not to have many routines built-in; the O[ interpreter is simpler and faster as a result.
So, print is needed often: make it a built-in. And, get not needed often: belongs to an include file.
p.s. In my services I accept the sequence {..., ...} and answer them {..., ...}(as others do it with json or xml). and this is the problem of those who seek to understand the format of standard format strings.
When learning O[ you must understand that everything is a number.
Try reading http://openeuphoria.org/wiki/view/The%20All%20Mighty%20Object.wc to get an idea of how things work.
The string "Hello" becomes {72,101,108,108,111} in Euphoria--there is no string data-type.
sequence str = "Hello" print(1, str ) --> {72,101,108,108,111} -- converted to numbers not a string data-type puts(1, {72,101,108,108,111} ) --> Hello puts(1, str) --> Hello -- you can always display a sequence of integers to look like a string
Most of the time the idea "accept and answer" works as if there was a string data-type.
When saving and then reading sequences you will have to remember the intended use of each item in the sequence. An item in a sequence is not atuomatically identified as a number or a string.
If you provide a sample of the data you are writing and reading it will be easier to explain how this works.
_tom
6. Re: I do not find in the documentation 4.XX describe GET
- Posted by useful Mar 19, 2014
- 1377 views
Alas, they are (http://translate.yandex.ru/) English is not as good as we would like, but it's better than mine. :) Will try again. I clearly understand how to work with sequences and doing it for many years.
I wrote that I for my project is almost always sufficient built-in functions, and only for the get, I should include get.e.
And I think it's not logical. As for example for XBASE the basis of the outside world it DBF, and for MUMPS GLOBALS and I hardly know what to write them built and read the external function.
7. Re: I do not find in the documentation 4.XX describe GET
- Posted by jimcbrown (admin) Mar 20, 2014
- 1308 views
I wrote that I for my project is almost always sufficient built-in functions, and only for the get, I should include get.e.
And I think it's not logical. As for example for XBASE the basis of the outside world it DBF, and for MUMPS GLOBALS and I hardly know what to write them built and read the external function.
I agree. This is a leftover from Rob Craig: http://openeuphoria.org/forum/41899.wc
I'd like to go the other way and see print() become a library (not builtin) function, but that's unlikely to happen. I consider print() obsolete anyways, pretty_print() is superior in virtually every way.
I don't see an issue with get() becoming a builtin, just no one has contributed a patch to do this yet - and writing a version in pure C is not so simple.
