Issue 84347 - Basic library names should NOT be case sensitive
Summary: Basic library names should NOT be case sensitive
Status: CLOSED DUPLICATE of issue 54601
Alias: None
Product: App Dev
Classification: Unclassified
Component: scripting (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P4 Trivial
Target Milestone: ---
Assignee: ab
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-07 15:41 UTC by bmarcelly
Modified: 2017-05-20 09:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0
Developer Difficulty: ---


Attachments
Document with AA and aa libraries (23.16 KB, application/vnd.oasis.opendocument.text)
2007-12-07 15:42 UTC, bmarcelly
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bmarcelly 2007-12-07 15:41:27 UTC
Next attachment is a document which contains a Basic library "AA"
With the library organizer user interface, another Basic library named "aa" was 
created.
This shows that the user interface is case sensitive about library names.

However from another library, e.g. from Standard, you only have access to the 
routines of one of these libraries. The identification path used by Basic is NOT case 
sensitive.

A side effect is that you can inadvertently create a "twin" library just by making an 
incorrect lower or upper case on a letter of the library name.

This happens also using the API.

Same problem with "My Macros".
Comment 1 bmarcelly 2007-12-07 15:42:23 UTC
Created attachment 50175 [details]
Document with AA and aa libraries
Comment 2 kay.ramme 2007-12-10 12:01:28 UTC
->AB: Please take care of this ...
Comment 3 ab 2007-12-13 14:34:41 UTC
The API cannot be changed any more as this would be incompatible
and I'm not sure about what can be done in the User Interface. My
only idea is to convert all library names to lower case, but I don't like
this idea very much. Anyway I don't think this is a very serious problem
as it's very easy to avoid. STARTED, OOLater, P4
Comment 4 ab 2007-12-14 14:49:33 UTC
STARTED, next try
Comment 5 mroe 2014-05-20 13:22:20 UTC
DUPLICATE issue 54601

*** This issue has been marked as a duplicate of issue 54601 ***