RE: Defining long constants - do-able but not exactly elegant
- Posted by bensler at mail.com Mar 14, 2002
- 472 views
What are you using to read in the file data? get(), gets() or getc()? Can you give an example of what is taking so long? I used to play with Eu on my 486DX 100mhz, and I never noticed any significant file loading times. Granted, I never tried opening any 50Mb files. Chris Kat wrote: > On 14 Mar 2002, at 0:55, Andy Serpa wrote: > > > > > Kat wrote: > > > > > > What's wrong with simply gets()ing a text file of any length you want, > > > edited > > > any way you want, and displayed any way you want, in any editor you > > > want, rather than cluttering up the code files? > > > > > > > Yeah, that's what I was gonna say. The rules for #3 don't preclude you > > from loading in any file you want (except machine code, or something > > like that). The program I'm working on loads in a "pre-hashed" > > dictionary, along with some other stuff, instead of wasting time on that > > > > everytime it starts.... > > I found loading the pre-munged data took way longer than grabbing the > plain > dictionary. Near as i can tell, it's the stuffing into 3-deep nested > sequences > that is eating the time. Maybe i should try making them a set length in > each > nest with the repeat() from the start. But munging dictionaries took > forever > too. Anyhoo, like i said, i am out of the contest, i can write the code, > but it > won't execute in time. It's so wierd, because the grammar parser runs > faster > than loading the dictionary for this contest. > > What bugs me a little about real-world apps using these cypto-solvers is > that > anyone with a reason to use them would have more than one paragraph to > solve, and loading and dictionary munging time would be inconsequential, > > because they'd be turned on and left running, looking for input. (I > leave one > mining program running sometimes, it goes active when the other programs > > feed it an url.) But then, these guys have load time down to sub-second > times, so,, errr, nevermind. > > Kat > >