Re: Patch for the handling of symbols in clsql

Howdy Kevin,

I don't think we should be run into any issues related to Allegro as 
regards this particular issue, because we are printing and reading 
symbols using the prin1-to-string and read-from-string, which should 
just handle that directly however Allegro has it configured.

I have had a couple bug reports with modern-mode on some other of my 
projects when I accidentally had mixed case symbols (and I believe 
iterate also used to cause some trouble).  I dont recall having any 
issues as regards Allegro and CLSQL, but not being an Allegro user 
probably has more to do with that than any skill on my part.  I mostly 
try to code in lowercase and hope for the best or bug reports as regards 
Allegro.

Cheers and thanks,
Russ Tyndall


On 04/24/2014 11:29 AM, Kevin Rosenberg wrote:
> On Apr 23, 2014, at 2:42 PM, Russ Tyndall <[email protected]> wrote:
>> I made a first draft at fixing the symbols issue we had been
>> discussing.  While tackling this I also knocked out the 2 TODOs in
>> [...]
> Thanks for working on this, Russ. As I wrote CLSQL, creating and
> maintaining support for Allegro's modern mode required unpleasant
> added complexity. Have you encountered much issues with supporting
> Allegro's "modern" case system?
>
> Kevin
>
> _______________________________________________
> CLSQL mailing list
> [email protected]
> http://lists.b9.com/cgi-bin/mailman/listinfo/clsql