Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symbol construction fix. #8

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Conversation

nzioki
Copy link

@nzioki nzioki commented Dec 26, 2016

Symbol is INTERN'ed in lower case when print-case is :downcase and
oodml.lisp fails to compile.

Martin Nzioki added 7 commits December 26, 2016 17:59
Symbol is INTERN'ed in lower case when *print-case* is :downcase and
oodml.lisp fails to compile.
Not the best approach but will have to do for now.
Lispworks: parameter SLOT-DEF in SLOT-VALUE-USING-CLASS() is a slot name
not slot instance.
By default, Lispworks does not call the SLOT-VALUE-USING-CLASS()
methods when reading or writing slot values but instead uses optimized
accessors. This behaviour is disabled by setting the :OPTIMIZE-SLOT-ACCESS
class option to NIL.

This patch defaults to this behaviour unless overriden.
Non-recursive lock fails for ODBC as API attempts to reuse query objects
since the same lock is utilized.

(Better fix needed?)
@bobbysmith007
Copy link
Collaborator

This looks mostly good, though I am curious about your changes to the package files.

I also dont understand the change from the :export clause of the defpackage to the (export) fn call with interned symbols - or why this was desirable or necessary? If it was desirable or necessary, why was it not done to all packages

@nzioki
Copy link
Author

nzioki commented Jan 16, 2017 via email

@bobbysmith007
Copy link
Collaborator

Sorry that I spaced on this for a year. Do you happen to remember what was wrong with the format variant vs the concatenate variant?

I can see certain printer settings affecting the format.

I am finally getting around to working on this again, so I am trying to integrate the important changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants