why binary field doesn't just use the syntax of fasm?

using the # character is something i really dislike. like using #$ in poor motorola assemblers...

Ah, the format of the data fields is simplified now. I decided, that there are many data formats and I can't handle all of them.
Now the library supports only integer numbers (in FASM format), plain string data and NULL fields. The user can parse the strings later in whatever way he wants - for example the string can contains BASE64 encoded binary data, or IP address, or URL encoded text or whatever.
This approach is IMHO more flexible than to try to handle different data types.