Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.soft-sys.math.mathematica > #7444 > unrolled thread
| Started by | Oliver Ruebenkoenig <ruebenko@wolfram.com> |
|---|---|
| First post | 2011-12-26 22:31 +0000 |
| Last post | 2011-12-26 22:31 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.soft-sys.math.mathematica
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Span Set nasty bug Oliver Ruebenkoenig <ruebenko@wolfram.com> - 2011-12-26 22:31 +0000
| From | Oliver Ruebenkoenig <ruebenko@wolfram.com> |
|---|---|
| Date | 2011-12-26 22:31 +0000 |
| Subject | Re: Span Set nasty bug |
| Message-ID | <jdask4$kei$1@smc.vnet.net> |
On Mon, 26 Dec 2011, Shizu wrote:
> Hello there,
> I think Roby's logic is right. Oliver's suggestion makes both results wrong -- t[[1,1]] should not be set to 1.
> The rule ("TableCompileLength" -> 1) is not documented. Span "1;;0" is not documented either.
This was to illustrate the the behavior can be changed. This is an issue
with packed arrays. So unpacking (or setting "TableCompileLength" ->
Infinity) using Developer`FromPackedArray is a better option.
> It's not safe to use something that is not documented.
>
That is right, you should be cautious.
As Rob mentioned this is with tech support now and is investigated.
Oliver
> You may want to invent your own version of Set[] for matrices.
>
>
Back to top | Article view | comp.soft-sys.math.mathematica
csiph-web