get() currently requires whitespace after each object. This seems unnecessary to me; stuff like 1234"text string in quotes" isn't pretty, but it's still two distinct, legitimate objects that can easily be distinquished by a modified get().
Besides, allowing things to be consecutive is more consistent with the documented behavior of value(), in the way it gets what it can and stops. Not that I recommend doing it that way; I imagine most people, including myself, would still naturally put space between things. It just seems unnecessary to enforce that beyond the self-enforcement of the data itself (e.g. you have to separate two numbers if you want them recognized as two rather than one, obviously...).
In addition, well, I sorta already did it that way before I realized it was wrong (working on updating get.e); putting the restriction back in kind of feels like crippling working code.
I will attempt to upload an updated get.e to the thread in which I asked a question about some other features. http://openeuphoria.org/forum/120973.wc
Woops, don't see how to upload a file, so here's the pastey link: http://openeuphoria.org/pastey/209.wc
bugreport.ex output
Version
----------------------------
4.0.5 development (5743:62d94559f849, 2012-10-15 09:43:49)
Operating System
----------------------------
Platform: Linux, Build: wotsit, 3.2.0-4-486:0
Include Directories
----------------------------
1: /home/user/bin/euphoria/include/
2: /home/user/downloads
3: /home/user/bin/euphoria/include
EUDIR
----------------------------
/home/user/bin/euphoria
PATH
----------------------------
/home/user/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/user/bin/euphoria/bin:/home/user/scripts:.
I'm back-pedaling on this one; some bugs I'm chasing in my get.e update efforts have convinced me there may be good reason for the spacing, at least in this implementation.