[DGD] Latest errors

[Stephen Spiller]

Makes sense.  I'll take a look.  It should handle \n and \r\n automagically.
 


> From: shentino at gmail.com
> Date: Fri, 13 Apr 2012 18:48:29 -0700
> To: dgd at dworkin.nl
> Subject: Re: [DGD] Latest errors
> 
> On Fri, Apr 13, 2012 at 6:34 PM, Stephen Spiller <steve_spiller at msn.com> wrote:
> >
> > That sure seems like a bug to me... DGD compiles natively on Win32 so it should also be able to handle the line endings. If no one else cares to look at it, perhaps I'll dink with it if I can get a spare hour or two sometime. :) -Steve
> 
> DGD can handle line endings just fine, however LPC code that reads
> file information reads it verbatim and doesn't implicitly translate it
> between win32 and unix style line endings.
> 
> What might help improve it though is allowing DGD's parse string
> function to digest either type of line ending in the grammar.
> 
> I'm guessing that's what it choked on, a CR-LF in the grammar.
> 
> 
> 
> > > From: shentino at gmail.com
> >> Date: Fri, 13 Apr 2012 17:25:09 -0700
> >> To: dgd at dworkin.nl
> >> Subject: Re: [DGD] Latest errors
> >>
> >> I found out what the problem is.
> >>
> >> Apparently your files have win32 style line endings with CR-LF.
> >>
> >> Try converting all the files to unix style LF line endings and that
> >> should fix it. I did it on my end and that solved it.
> >>
> >> On Fri, Apr 13, 2012 at 4:45 PM, Shentino <shentino at gmail.com> wrote:
> >> > I have attempted to reproduce this error without success.
> >> >
> >> >
> >> > On Fri, Apr 13, 2012 at 3:23 PM, Burning Steel Hammer
> >> > <burningsteelhammer at gmail.com> wrote:
> >> >> Okay, so after Shentino helped me out with where the various files/folders
> >> >> are actually supposed to go, this is what I get now:
> >> >>
> >> >> C:\dgd\bin>dgd c:/dgd/mud.dgd
> >> >> Apr 12 04:55:49 ** DGD 1.4.13
> >> >> Apr 12 04:55:49 ** Initializing...
> >> >> Apr 12 04:55:50 ** This is a very new Kernel Library version, or at
> >> >> Apr 12 04:55:50 ** least newer than this version of Phantasmal. If
> >> >> Apr 12 04:55:50 ** you have problems, please upgrade Phantasmal!
> >> >> Apr 12 04:55:51 ** Runtime error: Rule 2: bad token [caught]
> >> >> 440 initialize /kernel/sys/driver
> >> >> 423 _initialize /kernel/sys/driver
> >> >> 629 initd /kernel/sys/rsrcd
> >> >> 359 compile_object /kernel/lib/auto (/kernel/sys/rsrcd)
> >> >> 175 create /usr/System/initd
> >> >> 78 start_channels /usr/System/sys/logd
> >> >> 834 load /usr/common/obj/unq_dtd (#63)
> >> >> 22 basic_unq_parse /usr/common/obj/basic_unq_parser
> >> >> Apr 12 04:55:51 ** Runtime error: Can't parse UNQ data passed to
> >> >> unq_dtd:load!
> >> >> 440 initialize /kernel/sys/driver
> >> >> 423 _initialize /kernel/sys/driver
> >> >> 629 initd /kernel/sys/rsrcd
> >> >> 359 compile_object /kernel/lib/auto (/kernel/sys/rsrcd)
> >> >> 175 create /usr/System/initd
> >> >> 78 start_channels /usr/System/sys/logd
> >> >> 837 load /usr/common/obj/unq_dtd (#63)
> >> >> Apr 12 04:55:51 ** Initialization failed.
> >> >>
> >> >>
> >> >> *Note that I'm using the most recent Phantasmal from Shentino's repo.
> >> >> Everything else is as current as I know of.
> >> >> ___________________________________________
> >> >> https://mail.dworkin.nl/mailman/listinfo/dgd
> >> ___________________________________________
> >> https://mail.dworkin.nl/mailman/listinfo/dgd
> >
> > ___________________________________________
> > https://mail.dworkin.nl/mailman/listinfo/dgd
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd