From mint-bounce@lists.fishpool.fi Sun Dec 6 11:17:44 2009 Message-ID: <4B1BD8CA.9030104@atari-source.org> Date: Sun, 06 Dec 2009 11:16:10 -0500 From: Mark Duckworth User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Paul Wratt CC: mint Subject: Re: [MiNT] XaAES crash errors References: <11a6f2b10912031803h290d38a8i916fc270ce6c6d76@mail.gmail.com> <11a6f2b10912050321p7918ef60gb17ba429f719b4e9@mail.gmail.com> <752526d20912050438o49cf5e4fw37e1d423afcd2935@mail.gmail.com> <11a6f2b10912050915r6e8d3e5ejfec9970990326f25@mail.gmail.com> <1260041054.3156.1.camel@joy> <11a6f2b10912051203i6d9d5f33g7f163b46e10f2031@mail.gmail.com> In-Reply-To: <11a6f2b10912051203i6d9d5f33g7f163b46e10f2031@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Paul Wratt wrote: > 2009/12/6 Petr Stehlik : > >> Paul Wratt píše v Ne 06. 12. 2009 v 04:15 +1100: >> >>> The question: how do I pass "char *line" through to an intermediate >>> function that can then pass "&line" correctly. Would passing "*line" >>> be enough.. >>> >>> Truely, the biggest problem I am having, is knowing what terms to use >>> when I search for things. >>> >> Right now you're searching for a "Programming in C" book. In a library >> or a book store, probably. >> >> Petr >> > probably, especially if I was going to be a C programmer, but I am > here to fix and upgrade XaAES, which requires more than any book can > provide. > > I was hoping there was enough people here to allow me to get it done > fairly quickly, at least to a respectable v1 release that works 100% > across all platforms.. > > Paul > > > As other people are trying to imply, you will be of little real assistance without intimately understanding C because you will possibly (likely?) create many new pointer/buffer handling bugs. Thanks, Mark