Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
1996
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 1996

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: 3.0 = Rip Roaring Resource Hog :-(

  • To: mathgroup at smc.vnet.net
  • Subject: [mg5184] Re: [mg5094] 3.0 = Rip Roaring Resource Hog :-(
  • From: dreece at atl.mindspring.com (Daryl Reece)
  • Date: Sat, 9 Nov 1996 02:23:58 -0500
  • Organization: MindSpring Enterprises, Inc.
  • Sender: owner-wri-mathgroup at wolfram.com

I like the generality of Mathematica.  It's this generality that will
allow you to write this ByteArray header if you want.  See if
stripping off MMA's headers will reduce the size significantly.  I
believe the problem with specialized data structures is then writing
the rules and code to allow existing functions to deal with them.

Regarding your comment about resources.  Remember your time is
probably the most precious resource so if spending $1000 on RAM will
allow you to formulate problems 100% faster, I'd say it's a good
trade.

-Daryl

Mark Evans <evans at gte.net> wrote:


>I would prefer if Mathematica would let me, the user, decide just how much 
>generality to sacrifice to memory and time constraints.  If Mathematica had an 
>object like ByteArray[], then I myself could choose whether to put my data into 
>a List[] or ByteArray[], depending on my needs.  Programs like LabVIEW, for 
>example, let the programmer decide about the data type but still handle the 
>underlying memory management and loop iteration issues for him.

>That's emPOWerment!

>Mark








  • Prev by Date: Speeding Computations w/ NIntegrate[]
  • Next by Date: Re: Mathematica 3.0 for Linux?
  • Previous by thread: Re: 3.0 = Rip Roaring Resource Hog :-(
  • Next by thread: Re: error message