Excess values in #[..] construct on input do not give error, except for date

[Siskin-Bot]

Submitted by: meijeru

Apparently, after the required values (which sometimes can vary in number) one can add any number of values that are not checked or taken into account. Exception: #[date! ...] is critical.

>> #[decimal! 1]
== 1.0
>> #[decimal! 1 2 3 4 5]
== 1.0
>> #[image! 1x1 #{000000} #{00}]
== make image! [1x1 #{000000} #{00}]
>> #[image! 1x1 #{000000} a b c]
== make image! [1x1 #{000000}] ; a b c plainly ignored, even though a is in the place where a binary! value could be expected
>> #[date! 1 2 3 4:0 5:0]
== 1-Feb-0003/4:00+5:00
>> #[date! 1 2 3 4:0 5:0 6]
** Error

---

^{Imported from: CureCode [ Version: alpha 65 Type: Bug Platform: All Category: n/a Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1034}

Comments:

Rebolbot commented on Jul 1, 2009:

Submitted by: BrianH

This bug is more critical than it sounds: If we don't throw an error for extra stuff in the serialized expression, that extra stuff can block us in the future if we need to add more legitimate parameters. Screening for that makes us more future-proof.

---

Rebolbot mentioned this issue on Jan 12, 2016:
LOAD and MAKE of image! ignore series index

---

Rebolbot added the Type.bug on Jan 12, 2016

---

[Oldes]

I consider it partially resolved as I was not going thru all construction types... just here mentioned decimal!, image! and any-string!.. it now throws an error like:

>> #[file! "aa" 2 x]
** Syntax error: invalid construction spec: [file! "aa" 2 x]